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

       systemd.scope - Scope unit configuration


       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.

   Implicit Dependencies
       Implicit dependencies may be added as result of resource control
       parameters as documented in systemd.resource-control(5).

   Default Dependencies
       The following dependencies are added unless DefaultDependencies=no is

       o   Scope units will automatically 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
           DefaultDependencies= option.

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

        1. New Control Group Interfaces

systemd 239                                                   SYSTEMD.SCOPE(5)

Man(1) output converted with man2html
list of all man pages