diff options
author | Lennart Poettering <lennart@poettering.net> | 2013-07-19 19:16:47 +0200 |
---|---|---|
committer | Lennart Poettering <lennart@poettering.net> | 2013-07-19 19:16:47 +0200 |
commit | 847ae0ae7f29e7bfb245d692409fc2948eab7d1d (patch) | |
tree | d2e7acc093b9367a18c3d07e48e00c2d501b5400 /man/systemd.slice.xml | |
parent | 9365b048c0c9f62ef7f696216ba049e6b4c2f2e5 (diff) |
man: update documentation of slice units a bit
Diffstat (limited to 'man/systemd.slice.xml')
-rw-r--r-- | man/systemd.slice.xml | 34 |
1 files changed, 28 insertions, 6 deletions
diff --git a/man/systemd.slice.xml b/man/systemd.slice.xml index 5376921689..7ddef85eec 100644 --- a/man/systemd.slice.xml +++ b/man/systemd.slice.xml @@ -55,14 +55,34 @@ along with systemd; If not, see <http://www.gnu.org/licenses/>. <title>Description</title> <para>A unit configuration file whose name ends in - <literal>.slice</literal> encodes information about a slice - created by systemd to manage resources used by a certain group of + <literal>.slice</literal> encodes information about a slice which + is a concept for hierarchially managing resources of a group of processes. This management is performed by creating a node in the - control group tree. Those processes are part of different units, - usually <literal>.service</literal> units (see - <citerefentry><refentrytitle>systemd.unit</refentrytitle><manvolnum>5</manvolnum></citerefentry>). + control group tree. Units that manage processes (primarilly scope + and service units) may be assigned to a specific slice. For each + slice certain resource limits may the be set, that apply to all + processes of all units contained in that slice. Slices are + organized hierarchially in a tree. The name of the slice encodes + the location in the tree. The name consists of a "-" separated + series of names, which describes the path to the slice from the + root slice. The root slice is named, + <filename>-.slice</filename>. Example: + <filename>foo-bar.slice</filename> is a slice that is located + within <filename>foo.slice</filename>, which in turn is located in + the root slice <filename>-.slice</filename>. </para> + <para>By default service and scope units are placed in + <filename>system.slice</filename>, virtual machines and containers + registered with + <citerefentry><refentrytitle>systemd-machined</refentrytitle><manvolnum>1</manvolnum></citerefentry> + are found in <filename>machine.slice</filename>, and user sessions + handled by + <citerefentry><refentrytitle>systemd-logind</refentrytitle><manvolnum>1</manvolnum></citerefentry> + in <filename>user.slice</filename>. See + <citerefentry><refentrytitle>systemd.special</refentrytitle><manvolnum>5</manvolnum></citerefentry> + for more information.</para> + <para>See <citerefentry><refentrytitle>systemd.unit</refentrytitle><manvolnum>5</manvolnum></citerefentry> for the common options of all unit configuration @@ -92,7 +112,9 @@ along with systemd; If not, see <http://www.gnu.org/licenses/>. <citerefentry><refentrytitle>systemd.unit</refentrytitle><manvolnum>5</manvolnum></citerefentry>, <citerefentry><refentrytitle>systemd.cgroup</refentrytitle><manvolnum>5</manvolnum></citerefentry>, <citerefentry><refentrytitle>systemd.service</refentrytitle><manvolnum>5</manvolnum></citerefentry>, - <citerefentry><refentrytitle>systemd.directives</refentrytitle><manvolnum>7</manvolnum></citerefentry>. + <citerefentry><refentrytitle>systemd.scope</refentrytitle><manvolnum>5</manvolnum></citerefentry>, + <citerefentry><refentrytitle>systemd.special</refentrytitle><manvolnum>7</manvolnum></citerefentry>, + <citerefentry><refentrytitle>systemd.directives</refentrytitle><manvolnum>7</manvolnum></citerefentry> </para> </refsect1> |