Scope units are not configured via unit configuration files, but are
only created programmatically using the bus interfaces of systemd.
They are named similar to filenames. A unit whose name ends in
".scope" refers to a scope unit. Scopes units manage a set of system
processes. Unlike service units, scope units manage externally
created processes, and do not fork off processes on its own.
The main purpose of scope units is grouping worker processes of a
system service for organization and for managing resources.
systemd-run --scope may be used to easily launch a command in a new
scope unit from the command line.
See the New Control Group Interfaces for an introduction on how to
make use of scope units from programs.
Unless DefaultDependencies=false is used, scope units will implicitly
have dependencies of type Conflicts= and Before= on shutdown.target.
These ensure that scope units are removed prior to system shutdown.
Only scope units involved with early boot or late system shutdown
should disable this option.
Additional implicit dependencies may be added as result of resource
control parameters as documented in systemd.resource-control(5).
This page is part of the systemd (systemd system and service manager)
project. Information about the project can be found at
⟨http://www.freedesktop.org/wiki/Software/systemd⟩. If you have a bug
report for this manual page, see
page was obtained from the project's upstream Git repository
⟨https://github.com/systemd/systemd.git⟩ on 2017-03-13. If you dis‐
cover any rendering problems in this HTML version of the page, or you
believe there is a better or more up-to-date source for the page, or
you have corrections or improvements to the information in this
COLOPHON (which is not part of the original manual page), send a mail
systemd 233 SYSTEMD.SCOPE(5)