NAME<\/a> systemd.scope \u2212 Scope unit configuration<\/p>\n scope<\/i>.scope<\/p>\n 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.<\/p>\n The main purpose of scope units is grouping worker processes of a system service for organization and for managing resources.<\/p>\n systemd\u2212run \u2212\u2212scope<\/b> may be used to easily launch a command in a new scope unit from the command line.<\/p>\n See the New Control Group Interfaces<\/font><\/b> [1]<\/font><\/small> for an introduction on how to make use of scope units from programs.<\/font><\/p>\n Note that, unlike service units, scope units have no “main” process: all processes in the scope are equivalent. The lifecycle of the scope unit is thus not bound to the lifetime of one specific process, but to the existence of at least one process in the scope. This also means that the exit statuses of these processes are not relevant for the scope unit failure state. Scope units may still enter a failure state, for example due to resource exhaustion or stop timeouts being reached, but not due to programs inside of them terminating uncleanly. Since processes managed as scope units generally remain children of the original process that forked them off, it is also the job of that process to collect their exit statuses and act on them as needed.<\/font><\/p>\n Implicit Dependencies<\/b> Default Dependencies<\/b> \u2022 Scope units will automatically have dependencies of type Conflicts=<\/i> and Before=<\/i> 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 DefaultDependencies=<\/i> option.<\/font><\/p>\n Scope files may include a [Scope] section, which carries information about the scope and the units it contains. A number of options that may be used in this section are shared with other unit types. These options are documented in systemd.kill<\/b>(5) and systemd.resource-control<\/b>(5). The options specific to the [Scope] section of scope units are the following:<\/font><\/p>\n RuntimeMaxSec=<\/i><\/font><\/p>\n Configures a maximum time for the scope to run. If this is used and the scope has been active for longer than the specified time it is terminated and put into a failure state. Pass “infinity” (the default) to configure no runtime limit.<\/font><\/p>\n systemd<\/b>(1), systemd-run<\/b>(1), systemd.unit<\/b>(5), systemd.resource-control<\/b>(5), systemd.service<\/b>(5), systemd.directives<\/b>(7).<\/font><\/p>\n 1.<\/font><\/p>\n<\/td>\n New Control Group Interfaces<\/font><\/p>\n<\/td>\n https:\/\/www.freedesktop.org\/wiki\/Software\/systemd\/ControlGroupInterface\/<\/font><\/p>\n systemd.scope \u2212 Scope unit configuration <\/p>\n","protected":false},"author":1,"featured_media":0,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[959],"tags":[961,1291,978],"class_list":["post-4454","post","type-post","status-publish","format-standard","hentry","category-5-formatos-de-ficheros","tag-961","tag-man5","tag-systemd"],"gutentor_comment":0,"_links":{"self":[{"href":"https:\/\/lode.uno\/linux-man\/wp-json\/wp\/v2\/posts\/4454","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/lode.uno\/linux-man\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/lode.uno\/linux-man\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/lode.uno\/linux-man\/wp-json\/wp\/v2\/users\/1"}],"replies":[{"embeddable":true,"href":"https:\/\/lode.uno\/linux-man\/wp-json\/wp\/v2\/comments?post=4454"}],"version-history":[{"count":0,"href":"https:\/\/lode.uno\/linux-man\/wp-json\/wp\/v2\/posts\/4454\/revisions"}],"wp:attachment":[{"href":"https:\/\/lode.uno\/linux-man\/wp-json\/wp\/v2\/media?parent=4454"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/lode.uno\/linux-man\/wp-json\/wp\/v2\/categories?post=4454"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/lode.uno\/linux-man\/wp-json\/wp\/v2\/tags?post=4454"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}
SYNOPSIS<\/a>
DESCRIPTION<\/a>
AUTOMATIC DEPENDENCIES<\/a>
OPTIONS<\/a>
SEE ALSO<\/a>
NOTES<\/a> <\/p>\n
\nNAME <\/a> <\/h2>\n
SYNOPSIS <\/a> <\/h2>\n
DESCRIPTION <\/a> <\/h2>\n
AUTOMATIC DEPENDENCIES <\/a> <\/h2>\n
Implicit dependencies may be added as result of resource control parameters as documented in systemd.resource-control<\/b>(5).<\/font><\/p>\n
The following dependencies are added unless DefaultDependencies=no<\/i> is set:<\/font><\/p>\nOPTIONS <\/a> <\/h2>\n
SEE ALSO <\/a> <\/h2>\n
NOTES <\/a> <\/h2>\n
\n
\n <\/td>\n \n <\/td>\n \n <\/td>\n<\/tr>\n<\/table>\n
\n","protected":false},"excerpt":{"rendered":"