2018-07-03 00:15:39 +03:00
<?xml version='1.0'?>
2013-07-10 09:25:02 +04:00
< !DOCTYPE refentry PUBLIC "-//OASIS//DTD DocBook XML V4.2//EN"
2015-06-18 20:47:44 +03:00
"http://www.oasis-open.org/docbook/xml/4.2/docbookx.dtd">
2013-07-10 09:25:02 +04:00
<!--
2017-11-18 19:22:32 +03:00
SPDX-License-Identifier: LGPL-2.1+
2013-07-10 09:25:02 +04:00
-->
<refentry id= "systemd.scope" >
<refentryinfo >
<title > systemd.scope</title>
<productname > systemd</productname>
</refentryinfo>
<refmeta >
<refentrytitle > systemd.scope</refentrytitle>
<manvolnum > 5</manvolnum>
</refmeta>
<refnamediv >
<refname > systemd.scope</refname>
<refpurpose > Scope unit configuration</refpurpose>
</refnamediv>
<refsynopsisdiv >
<para > <filename > <replaceable > scope</replaceable> .scope</filename> </para>
</refsynopsisdiv>
<refsect1 >
<title > Description</title>
2013-07-19 21:04:17 +04:00
<para > 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 <literal > .scope</literal> refers to a scope unit. Scopes
2013-07-21 08:53:14 +04:00
units manage a set of system processes. Unlike service units, scope
2013-07-19 21:04:17 +04:00
units manage externally created processes, and do not fork off
processes on its own.</para>
2013-07-10 09:25:02 +04:00
2013-07-19 21:04:17 +04:00
<para > The main purpose of scope units is grouping worker processes
2013-07-19 21:16:47 +04:00
of a system service for organization and for managing resources.</para>
2013-07-19 21:04:17 +04:00
<para > <command > systemd-run <option > --scope</option> </command> may
be used to easily launch a command in a new scope unit from the
command line.</para>
2013-07-10 09:25:02 +04:00
2013-09-30 20:54:05 +04:00
<para > See the <ulink
2017-02-21 18:28:04 +03:00
url="https://www.freedesktop.org/wiki/Software/systemd/ControlGroupInterface/">New
2013-10-15 10:58:51 +04:00
Control Group Interfaces</ulink> for an introduction on how to make
2013-09-30 20:54:05 +04:00
use of scope units from programs.</para>
2015-11-11 22:47:07 +03:00
</refsect1>
<refsect1 >
2018-04-16 19:00:33 +03:00
<title > Automatic Dependencies</title>
<refsect2 >
<title > Implicit Dependencies</title>
<para > Implicit dependencies may be added as result of
resource control parameters as documented in
<citerefentry > <refentrytitle > systemd.resource-control</refentrytitle> <manvolnum > 5</manvolnum> </citerefentry> .</para>
</refsect2>
<refsect2 >
<title > Default Dependencies</title>
<para > The following dependencies are added unless
<varname > DefaultDependencies=no</varname> is set:</para>
<itemizedlist >
<listitem > <para > Scope units will automatically have dependencies of
type <varname > Conflicts=</varname> and
<varname > Before=</varname> on
<filename > shutdown.target</filename> . These ensure
that scope units are removed prior to system
shutdown. Only scope units involved with early boot or
late system shutdown should disable
<varname > DefaultDependencies=</varname> option.</para> </listitem>
</itemizedlist>
</refsect2>
2013-07-10 09:25:02 +04:00
</refsect1>
<refsect1 >
<title > See Also</title>
<para >
<citerefentry > <refentrytitle > systemd</refentrytitle> <manvolnum > 1</manvolnum> </citerefentry> ,
<citerefentry > <refentrytitle > systemd-run</refentrytitle> <manvolnum > 1</manvolnum> </citerefentry> ,
<citerefentry > <refentrytitle > systemd.unit</refentrytitle> <manvolnum > 5</manvolnum> </citerefentry> ,
2013-09-27 02:05:07 +04:00
<citerefentry > <refentrytitle > systemd.resource-control</refentrytitle> <manvolnum > 5</manvolnum> </citerefentry> ,
2013-07-10 09:25:02 +04:00
<citerefentry > <refentrytitle > systemd.service</refentrytitle> <manvolnum > 5</manvolnum> </citerefentry> ,
<citerefentry > <refentrytitle > systemd.directives</refentrytitle> <manvolnum > 7</manvolnum> </citerefentry> .
</para>
</refsect1>
</refentry>