NAME systemd.scope - Scope unit configuration SYNOPSIS scope .scope DESCRIPTION Scope units are not configuredNonBlocking= systemd.service (5) NotifyAccess= systemd.service (5) OOMPolicy= systemd.scope (5), systemd.service (5) OOMScoreAdjust= systemd.exec (5) OnActiveSec ... RuntimeDirecto…[email protected], in a scope unit. A systemd.scope (5) unit is used instead ... systemctl (1), systemd.unit (5), systemd.service (5), systemd.scope (5), systemd.slice (5), systemd.exe…systemd.path (5), systemd.timer (5), systemd.slice (5), systemd.scope (5). Unit files are loaded from ... systemd.target (5), systemd.path (5), systemd.timer (5), systemd.scope (5)…unit configuration files, and systemd.slice (5), systemd.scope (5), systemd.service (5), systemd.socket (5), systemd.mount ... systemd.unit (5), systemd.service (5), systemd.slice …instead of starting them as well. See systemd.scope (5). Units are named as their configurationsystemd.socket (5), systemd.swap (5), systemd.mount (5) and systemd.scope (5) for more information on the configurationsystemd.unit (5), systemd.resource-control (5), systemd.service (5), systemd.scope (5), systemd.special (7), systemd.directives (7) NOTESsystemd.path (5), systemd.timer (5), systemd.slice (5), systemd.scope (5) •link files, see systemd.link (5) •netdevsystemd.resource-control (5) — Resource control unit settings systemd.scope (5) — Scope unit configuration systemd.service (5) — Servicecase they form a .scope unit (see systemd.scope (5)). Both user@ UID .serviceunits contain programs launched by systemd, and systemd.scope (5) units contain programs launched by somethingfalse, the scope is "abandoned", see systemd.scope (5), and processes are not killed. Defaultsfalse, the scope is "abandoned", see systemd.scope (5), and processes are not killed. Defaults