SYSTEMD.SCOPE(5)                systemd.scope               SYSTEMD.SCOPE(5)

NAME         top

       systemd.scope - Scope unit configuration

SYNOPSIS         top


DESCRIPTION         top

       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[1] 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
       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).

SEE ALSO         top

       systemd(1), systemd-run(1), systemd.unit(5),
       systemd.resource-control(5), systemd.service(5),

NOTES         top

        1. New Control Group Interfaces

COLOPHON         top

       This page is part of the systemd (systemd system and service manager)
       project.  Information about the project can be found at 
       ⟨⟩.  If you have a bug
       report for this manual page, see
       ⟨⟩.  This
       page was obtained from the project's upstream Git repository
       ⟨⟩ on 2019-11-19.  (At that
       time, the date of the most recent commit that was found in the repos‐
       itory was 2019-11-19.)  If you discover 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 to

systemd 234                                                 SYSTEMD.SCOPE(5)

Pages that refer to this page: systemd(1)systemd-run(1)logind.conf(5)systemd.kill(5)systemd.resource-control(5)systemd.slice(5)systemd.unit(5)systemd.directives(7)systemd.index(7)pam_systemd(8)