2010-07-03 01:24:38 +04:00
<?xml version='1.0'?> <!-- * - nxml - * -->
<?xml-stylesheet type="text/xsl" href="http://docbook.sourceforge.net/release/xsl/current/xhtml/docbook.xsl"?>
< !DOCTYPE refentry PUBLIC "-//OASIS//DTD DocBook XML V4.2//EN"
"http://www.oasis-open.org/docbook/xml/4.2/docbookx.dtd">
<!--
This file is part of systemd.
Copyright 2010 Lennart Poettering
systemd is free software; you can redistribute it and/or modify it
2012-04-12 02:20:58 +04:00
under the terms of the GNU Lesser General Public License as published by
the Free Software Foundation; either version 2.1 of the License, or
2010-07-03 01:24:38 +04:00
(at your option) any later version.
systemd is distributed in the hope that it will be useful, but
WITHOUT ANY WARRANTY; without even the implied warranty of
MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the GNU
2012-04-12 02:20:58 +04:00
Lesser General Public License for more details.
2010-07-03 01:24:38 +04:00
2012-04-12 02:20:58 +04:00
You should have received a copy of the GNU Lesser General Public License
2010-07-03 01:24:38 +04:00
along with systemd; If not, see <http: / / w w w . g n u . o r g / l i c e n s e s /> .
-->
<refentry id= "systemd.exec" >
<refentryinfo >
<title > systemd.exec</title>
<productname > systemd</productname>
<authorgroup >
<author >
<contrib > Developer</contrib>
<firstname > Lennart</firstname>
<surname > Poettering</surname>
<email > lennart@poettering.net</email>
</author>
</authorgroup>
</refentryinfo>
<refmeta >
<refentrytitle > systemd.exec</refentrytitle>
<manvolnum > 5</manvolnum>
</refmeta>
<refnamediv >
<refname > systemd.exec</refname>
2012-07-16 20:08:25 +04:00
<refpurpose > Execution environment configuration</refpurpose>
2010-07-03 01:24:38 +04:00
</refnamediv>
<refsynopsisdiv >
2013-02-14 07:46:37 +04:00
<para > <filename > <replaceable > service</replaceable> .service</filename> ,
<filename > <replaceable > socket</replaceable> .socket</filename> ,
<filename > <replaceable > mount</replaceable> .mount</filename> ,
<filename > <replaceable > swap</replaceable> .swap</filename> </para>
2010-07-03 01:24:38 +04:00
</refsynopsisdiv>
<refsect1 >
<title > Description</title>
2011-05-27 09:24:22 +04:00
<para > Unit configuration files for services, sockets,
2011-01-18 02:40:10 +03:00
mount points and swap devices share a subset of
configuration options which define the execution
environment of spawned processes.</para>
2010-07-03 01:24:38 +04:00
<para > This man page lists the configuration options
2011-05-27 09:24:22 +04:00
shared by these four unit types. See
2010-07-03 01:24:38 +04:00
<citerefentry > <refentrytitle > systemd.unit</refentrytitle> <manvolnum > 5</manvolnum> </citerefentry>
for the common options of all unit configuration
files, and
2011-01-18 02:40:10 +03:00
<citerefentry > <refentrytitle > systemd.service</refentrytitle> <manvolnum > 5</manvolnum> </citerefentry> ,
<citerefentry > <refentrytitle > systemd.socket</refentrytitle> <manvolnum > 5</manvolnum> </citerefentry> ,
<citerefentry > <refentrytitle > systemd.swap</refentrytitle> <manvolnum > 5</manvolnum> </citerefentry>
2010-07-03 01:24:38 +04:00
and
<citerefentry > <refentrytitle > systemd.mount</refentrytitle> <manvolnum > 5</manvolnum> </citerefentry>
for more information on the specific unit
configuration files. The execution specific
configuration options are configured in the [Service],
Reword sentences that contain psuedo-English "resp."
As you likely know, Arch Linux is in the process of moving to systemd.
So I was reading through the various systemd docs and quickly became
baffled by this new abbreviation "resp.", which I've never seen before
in my English-mother-tongue life.
Some quick Googling turned up a reference:
<http://www.transblawg.eu/index.php?/archives/870-Resp.-and-other-non-existent-English-wordsNicht-existente-englische-Woerter.html>
I guess it's a literal translation of the German "Beziehungsweise", but
English doesn't work the same way. The word "respectively" is used
exclusively to provide an ordering connection between two lists. E.g.
"the prefixes k, M, and G refer to kilo-, mega-, and giga-,
respectively." It is also never abbreviated to "resp." So the sentence
"Sets the default output resp. error output for all services and
sockets" makes no sense to a natural English speaker.
This patch removes all instances of "resp." in the man pages and
replaces them with sentences which are much more clear and, hopefully,
grammatically valid. In almost all instances, it was simply replacing
"resp." with "or," which the original author (Lennart?) could probably
just do in the future.
The only other instances of "resp." are in the src/ subtree, which I
don't feel privileged to correct.
Signed-off-by: Andrew Eikum <aeikum@codeweavers.com>
2012-10-15 22:59:12 +04:00
[Socket], [Mount], or [Swap] sections, depending on the unit
2010-07-03 01:24:38 +04:00
type.</para>
</refsect1>
<refsect1 >
<title > Options</title>
2013-01-26 19:47:16 +04:00
<variablelist class= 'unit-directives' >
2010-07-03 01:24:38 +04:00
<varlistentry >
<term > <varname > WorkingDirectory=</varname> </term>
<listitem > <para > Takes an absolute
directory path. Sets the working
2012-07-16 14:44:42 +04:00
directory for executed processes. If
not set defaults to the root directory
when systemd is running as a system
instance and the respective user's
home directory if run as
user.</para> </listitem>
2010-07-03 01:24:38 +04:00
</varlistentry>
<varlistentry >
<term > <varname > RootDirectory=</varname> </term>
<listitem > <para > Takes an absolute
directory path. Sets the root
directory for executed processes, with
the
<citerefentry > <refentrytitle > chroot</refentrytitle> <manvolnum > 2</manvolnum> </citerefentry>
system call. If this is used it must
be ensured that the process and all
its auxiliary files are available in
the <function > chroot()</function>
jail.</para> </listitem>
</varlistentry>
<varlistentry >
<term > <varname > User=</varname> </term>
<term > <varname > Group=</varname> </term>
<listitem > <para > Sets the Unix user
Reword sentences that contain psuedo-English "resp."
As you likely know, Arch Linux is in the process of moving to systemd.
So I was reading through the various systemd docs and quickly became
baffled by this new abbreviation "resp.", which I've never seen before
in my English-mother-tongue life.
Some quick Googling turned up a reference:
<http://www.transblawg.eu/index.php?/archives/870-Resp.-and-other-non-existent-English-wordsNicht-existente-englische-Woerter.html>
I guess it's a literal translation of the German "Beziehungsweise", but
English doesn't work the same way. The word "respectively" is used
exclusively to provide an ordering connection between two lists. E.g.
"the prefixes k, M, and G refer to kilo-, mega-, and giga-,
respectively." It is also never abbreviated to "resp." So the sentence
"Sets the default output resp. error output for all services and
sockets" makes no sense to a natural English speaker.
This patch removes all instances of "resp." in the man pages and
replaces them with sentences which are much more clear and, hopefully,
grammatically valid. In almost all instances, it was simply replacing
"resp." with "or," which the original author (Lennart?) could probably
just do in the future.
The only other instances of "resp." are in the src/ subtree, which I
don't feel privileged to correct.
Signed-off-by: Andrew Eikum <aeikum@codeweavers.com>
2012-10-15 22:59:12 +04:00
or group that the processes are executed
as, respectively. Takes a single user or group
2010-07-03 01:24:38 +04:00
name or ID as argument. If no group is
Reword sentences that contain psuedo-English "resp."
As you likely know, Arch Linux is in the process of moving to systemd.
So I was reading through the various systemd docs and quickly became
baffled by this new abbreviation "resp.", which I've never seen before
in my English-mother-tongue life.
Some quick Googling turned up a reference:
<http://www.transblawg.eu/index.php?/archives/870-Resp.-and-other-non-existent-English-wordsNicht-existente-englische-Woerter.html>
I guess it's a literal translation of the German "Beziehungsweise", but
English doesn't work the same way. The word "respectively" is used
exclusively to provide an ordering connection between two lists. E.g.
"the prefixes k, M, and G refer to kilo-, mega-, and giga-,
respectively." It is also never abbreviated to "resp." So the sentence
"Sets the default output resp. error output for all services and
sockets" makes no sense to a natural English speaker.
This patch removes all instances of "resp." in the man pages and
replaces them with sentences which are much more clear and, hopefully,
grammatically valid. In almost all instances, it was simply replacing
"resp." with "or," which the original author (Lennart?) could probably
just do in the future.
The only other instances of "resp." are in the src/ subtree, which I
don't feel privileged to correct.
Signed-off-by: Andrew Eikum <aeikum@codeweavers.com>
2012-10-15 22:59:12 +04:00
set, the default group of the user is
2010-07-03 01:24:38 +04:00
chosen.</para> </listitem>
</varlistentry>
<varlistentry >
<term > <varname > SupplementaryGroups=</varname> </term>
<listitem > <para > Sets the supplementary
Unix groups the processes are executed
2010-09-03 18:30:48 +04:00
as. This takes a space separated list
2010-07-03 01:24:38 +04:00
of group names or IDs. This option may
be specified more than once in which
case all listed groups are set as
2013-01-17 05:27:06 +04:00
supplementary groups. When the empty
string is assigned the list of
supplementary groups is reset, and all
assignments prior to this one will
have no effect. In any way, this
option does not override, but extends
the list of supplementary groups
configured in the system group
database for the
2010-07-03 01:24:38 +04:00
user.</para> </listitem>
</varlistentry>
<varlistentry >
<term > <varname > Nice=</varname> </term>
<listitem > <para > Sets the default nice
level (scheduling priority) for
executed processes. Takes an integer
between -20 (highest priority) and 19
(lowest priority). See
<citerefentry > <refentrytitle > setpriority</refentrytitle> <manvolnum > 2</manvolnum> </citerefentry>
for details.</para> </listitem>
</varlistentry>
<varlistentry >
2010-08-31 03:33:39 +04:00
<term > <varname > OOMScoreAdjust=</varname> </term>
2010-07-03 01:24:38 +04:00
<listitem > <para > Sets the adjustment
level for the Out-Of-Memory killer for
executed processes. Takes an integer
2010-08-31 03:33:39 +04:00
between -1000 (to disable OOM killing
for this process) and 1000 (to make
2010-07-03 01:24:38 +04:00
killing of this process under memory
pressure very likely). See <ulink
url="http://www.kernel.org/doc/Documentation/filesystems/proc.txt">proc.txt</ulink>
for details.</para> </listitem>
</varlistentry>
<varlistentry >
<term > <varname > IOSchedulingClass=</varname> </term>
<listitem > <para > Sets the IO scheduling
class for executed processes. Takes an
integer between 0 and 3 or one of the
strings <option > none</option> ,
<option > realtime</option> ,
<option > best-effort</option> or
<option > idle</option> . See
<citerefentry > <refentrytitle > ioprio_set</refentrytitle> <manvolnum > 2</manvolnum> </citerefentry>
for details.</para> </listitem>
</varlistentry>
<varlistentry >
<term > <varname > IOSchedulingPriority=</varname> </term>
<listitem > <para > Sets the IO scheduling
priority for executed processes. Takes
an integer between 0 (highest
priority) and 7 (lowest priority). The
available priorities depend on the
selected IO scheduling class (see
above). See
<citerefentry > <refentrytitle > ioprio_set</refentrytitle> <manvolnum > 2</manvolnum> </citerefentry>
for details.</para> </listitem>
</varlistentry>
<varlistentry >
<term > <varname > CPUSchedulingPolicy=</varname> </term>
<listitem > <para > Sets the CPU
scheduling policy for executed
processes. Takes one of
<option > other</option> ,
<option > batch</option> ,
<option > idle</option> ,
<option > fifo</option> or
<option > rr</option> . See
<citerefentry > <refentrytitle > sched_setscheduler</refentrytitle> <manvolnum > 2</manvolnum> </citerefentry>
for details.</para> </listitem>
</varlistentry>
<varlistentry >
<term > <varname > CPUSchedulingPriority=</varname> </term>
<listitem > <para > Sets the CPU
scheduling priority for executed
2012-11-01 21:48:11 +04:00
processes. The available priority
2010-07-03 01:24:38 +04:00
range depends on the selected CPU
2012-11-01 21:48:11 +04:00
scheduling policy (see above). For
real-time scheduling policies an
integer between 1 (lowest priority)
and 99 (highest priority) can be used.
See <citerefentry > <refentrytitle > sched_setscheduler</refentrytitle> <manvolnum > 2</manvolnum> </citerefentry>
for details.
</para> </listitem>
2010-07-03 01:24:38 +04:00
</varlistentry>
<varlistentry >
<term > <varname > CPUSchedulingResetOnFork=</varname> </term>
<listitem > <para > Takes a boolean
argument. If true elevated CPU
scheduling priorities and policies
will be reset when the executed
processes fork, and can hence not leak
into child processes. See
<citerefentry > <refentrytitle > sched_setscheduler</refentrytitle> <manvolnum > 2</manvolnum> </citerefentry>
for details. Defaults to false.</para> </listitem>
</varlistentry>
<varlistentry >
<term > <varname > CPUAffinity=</varname> </term>
<listitem > <para > Controls the CPU
affinity of the executed
2010-09-03 18:30:48 +04:00
processes. Takes a space-separated
2013-01-17 05:27:06 +04:00
list of CPU indexes. This option may
be specified more than once in which
case the specificed CPU affinity masks
are merged. If the empty string is
assigned the mask is reset, all
assignments prior to this will have no
effect. See
2010-07-03 01:24:38 +04:00
<citerefentry > <refentrytitle > sched_setaffinity</refentrytitle> <manvolnum > 2</manvolnum> </citerefentry>
for details.</para> </listitem>
</varlistentry>
<varlistentry >
<term > <varname > UMask=</varname> </term>
<listitem > <para > Controls the file mode
creation mask. Takes an access mode in
octal notation. See
<citerefentry > <refentrytitle > umask</refentrytitle> <manvolnum > 2</manvolnum> </citerefentry>
for details. Defaults to
2011-08-02 00:37:45 +04:00
0022.</para> </listitem>
2010-07-03 01:24:38 +04:00
</varlistentry>
<varlistentry >
<term > <varname > Environment=</varname> </term>
<listitem > <para > Sets environment
variables for executed
2010-09-03 18:30:48 +04:00
processes. Takes a space-separated
2010-07-03 01:24:38 +04:00
list of variable assignments. This
option may be specified more than once
in which case all listed variables
will be set. If the same variable is
set twice the later setting will
2013-01-17 05:27:06 +04:00
override the earlier setting. If the
empty string is assigned to this
option the list of environment
variables is reset, all prior
2013-01-24 21:06:00 +04:00
assignments have no effect.
Variable expansion is not performed
inside the strings, and $ has no special
meaning.
If you need to assign a value containing spaces
to a variable, use double quotes (")
for the assignment.</para>
<para > Example:
<programlisting > Environment="VAR1=word1 word2" VAR2=word3 "VAR3=word 5 6"</programlisting>
gives three variables <literal > VAR1</literal> ,
<literal > VAR2</literal> , <literal > VAR3</literal> .
</para>
<para >
See
2010-07-03 01:24:38 +04:00
<citerefentry > <refentrytitle > environ</refentrytitle> <manvolnum > 7</manvolnum> </citerefentry>
2013-01-24 21:06:00 +04:00
for details about environment variables.</para> </listitem>
2010-07-03 01:24:38 +04:00
</varlistentry>
<varlistentry >
<term > <varname > EnvironmentFile=</varname> </term>
<listitem > <para > Similar to
<varname > Environment=</varname> but
reads the environment variables from a
text file. The text file should
2010-09-03 18:30:48 +04:00
contain new-line separated variable
2010-07-03 01:24:38 +04:00
assignments. Empty lines and lines
starting with ; or # will be ignored,
2013-01-18 13:05:10 +04:00
which may be used for commenting. A line
ending with a backslash will be concatenated
with the following one, allowing multiline variable
definitions. The parser strips leading
and trailing whitespace from the values
2011-10-03 14:50:09 +04:00
of assignments, unless you use
2013-01-17 05:27:06 +04:00
double quotes (").</para>
<para > The argument passed should be an
absolute file name or wildcard
expression, optionally prefixed with
2011-01-06 03:39:08 +03:00
"-", which indicates that if the file
does not exist it won't be read and no
2013-01-17 05:27:06 +04:00
error or warning message is logged.
This option may be specified more than
once in which case all specified files
are read. If the empty string is
assigned to this option the list of
file to read is reset, all prior
assignments have no effect.</para>
<para > The files listed with this
2011-03-04 16:13:47 +03:00
directive will be read shortly before
the process is executed. Settings from
these files override settings made
with
<varname > Environment=</varname> . If
the same variable is set twice from
these files the files will be read in
the order they are specified and the
later setting will override the
2013-01-17 05:27:06 +04:00
earlier setting.</para> </listitem>
2010-07-03 01:24:38 +04:00
</varlistentry>
<varlistentry >
<term > <varname > StandardInput=</varname> </term>
<listitem > <para > Controls where file
descriptor 0 (STDIN) of the executed
processes is connected to. Takes one
of <option > null</option> ,
<option > tty</option> ,
<option > tty-force</option> ,
<option > tty-fail</option> or
<option > socket</option> . If
<option > null</option> is selected
standard input will be connected to
<filename > /dev/null</filename> ,
i.e. all read attempts by the process
will result in immediate EOF. If
<option > tty</option> is selected
standard input is connected to a TTY
(as configured by
<varname > TTYPath=</varname> , see
below) and the executed process
becomes the controlling process of the
terminal. If the terminal is already
2010-11-11 16:24:47 +03:00
being controlled by another process the
executed process waits until the current
controlling process releases the
terminal.
<option > tty-force</option>
2010-07-03 01:24:38 +04:00
is similar to <option > tty</option> ,
but the executed process is forcefully
and immediately made the controlling
process of the terminal, potentially
removing previous controlling
processes from the
terminal. <option > tty-fail</option> is
similar to <option > tty</option> but if
the terminal already has a controlling
process start-up of the executed
process fails. The
<option > socket</option> option is only
valid in socket-activated services,
and only when the socket configuration
file (see
<citerefentry > <refentrytitle > systemd.socket</refentrytitle> <manvolnum > 5</manvolnum> </citerefentry>
for details) specifies a single socket
only. If this option is set standard
input will be connected to the socket
the service was activated from, which
is primarily useful for compatibility
with daemons designed for use with the
traditional
<citerefentry > <refentrytitle > inetd</refentrytitle> <manvolnum > 8</manvolnum> </citerefentry>
daemon. This setting defaults to
<option > null</option> .</para> </listitem>
</varlistentry>
<varlistentry >
<term > <varname > StandardOutput=</varname> </term>
<listitem > <para > Controls where file
descriptor 1 (STDOUT) of the executed
processes is connected to. Takes one
of <option > inherit</option> ,
<option > null</option> ,
<option > tty</option> ,
<option > syslog</option> ,
2011-02-15 03:27:53 +03:00
<option > kmsg</option> ,
2012-01-06 02:54:45 +04:00
<option > journal</option> ,
<option > syslog+console</option> ,
2011-02-15 03:27:53 +03:00
<option > kmsg+console</option> ,
2012-01-06 02:54:45 +04:00
<option > journal+console</option> or
2010-07-03 01:24:38 +04:00
<option > socket</option> . If set to
<option > inherit</option> the file
descriptor of standard input is
duplicated for standard output. If set
to <option > null</option> standard
output will be connected to
<filename > /dev/null</filename> ,
i.e. everything written to it will be
lost. If set to <option > tty</option>
standard output will be connected to a
tty (as configured via
<varname > TTYPath=</varname> , see
below). If the TTY is used for output
only the executed process will not
become the controlling process of the
terminal, and will not fail or wait
for other processes to release the
terminal. <option > syslog</option>
connects standard output to the
<citerefentry > <refentrytitle > syslog</refentrytitle> <manvolnum > 3</manvolnum> </citerefentry>
2011-08-31 00:42:49 +04:00
system syslog
service. <option > kmsg</option>
2010-07-03 01:24:38 +04:00
connects it with the kernel log buffer
which is accessible via
2012-01-06 02:54:45 +04:00
<citerefentry > <refentrytitle > dmesg</refentrytitle> <manvolnum > 1</manvolnum> </citerefentry> . <option > journal</option>
connects it with the journal which is
accessible via
2012-03-26 22:58:47 +04:00
<citerefentry > <refentrytitle > journalctl</refentrytitle> <manvolnum > 1</manvolnum> </citerefentry>
2012-01-06 02:54:45 +04:00
(Note that everything that is written
to syslog or kmsg is implicitly stored
in the journal as well, those options
are hence supersets of this
one). <option > syslog+console</option> ,
<option > journal+console</option> and
<option > kmsg+console</option> work
2011-02-15 03:27:53 +03:00
similarly but copy the output to the
system console as
well. <option > socket</option> connects
standard output to a socket from
socket activation, semantics are
2010-07-03 01:24:38 +04:00
similar to the respective option of
<varname > StandardInput=</varname> .
2011-08-31 00:57:55 +04:00
This setting defaults to the value set
with
<option > DefaultStandardOutput=</option>
in
2013-02-11 23:42:24 +04:00
<citerefentry > <refentrytitle > systemd-system.conf</refentrytitle> <manvolnum > 5</manvolnum> </citerefentry> ,
2011-08-31 00:57:55 +04:00
which defaults to
2012-01-06 02:54:45 +04:00
<option > journal</option> .</para> </listitem>
2010-07-03 01:24:38 +04:00
</varlistentry>
<varlistentry >
2010-07-07 05:24:38 +04:00
<term > <varname > StandardError=</varname> </term>
2010-07-03 01:24:38 +04:00
<listitem > <para > Controls where file
descriptor 2 (STDERR) of the executed
processes is connected to. The
available options are identical to
those of
2010-07-07 05:24:38 +04:00
<varname > StandardOutput=</varname> ,
2010-12-31 03:50:51 +03:00
with one exception: if set to
2010-07-03 01:24:38 +04:00
<option > inherit</option> the file
descriptor used for standard output is
duplicated for standard error. This
2011-08-31 00:57:55 +04:00
setting defaults to the value set with
<option > DefaultStandardError=</option>
in
2013-02-11 23:42:24 +04:00
<citerefentry > <refentrytitle > systemd-system.conf</refentrytitle> <manvolnum > 5</manvolnum> </citerefentry> ,
2011-08-31 00:57:55 +04:00
which defaults to
2010-07-03 01:24:38 +04:00
<option > inherit</option> .</para> </listitem>
</varlistentry>
<varlistentry >
<term > <varname > TTYPath=</varname> </term>
<listitem > <para > Sets the terminal
device node to use if standard input,
output or stderr are connected to a
TTY (see above). Defaults to
<filename > /dev/console</filename> .</para> </listitem>
</varlistentry>
2011-05-18 03:07:31 +04:00
<varlistentry >
<term > <varname > TTYReset=</varname> </term>
<listitem > <para > Reset the terminal
device specified with
<varname > TTYPath=</varname> before and
after execution. Defaults to
<literal > no</literal> .</para> </listitem>
</varlistentry>
<varlistentry >
<term > <varname > TTYVHangup=</varname> </term>
<listitem > <para > Disconnect all clients
which have opened the terminal device
specified with
<varname > TTYPath=</varname>
before and after execution. Defaults
to
<literal > no</literal> .</para> </listitem>
</varlistentry>
<varlistentry >
<term > <varname > TTYVTDisallocate=</varname> </term>
2012-09-04 21:24:16 +04:00
<listitem > <para > If the terminal
2011-05-18 03:07:31 +04:00
device specified with
<varname > TTYPath=</varname> is a
virtual console terminal try to
deallocate the TTY before and after
execution. This ensures that the
screen and scrollback buffer is
cleared. Defaults to
<literal > no</literal> .</para> </listitem>
</varlistentry>
2010-07-03 01:24:38 +04:00
<varlistentry >
2011-02-19 08:10:49 +03:00
<term > <varname > SyslogIdentifier=</varname> </term>
2010-07-03 01:24:38 +04:00
<listitem > <para > Sets the process name
to prefix log lines sent to syslog or
the kernel log buffer with. If not set
defaults to the process name of the
executed process. This option is only
useful when
<varname > StandardOutput=</varname> or
<varname > StandardError=</varname> are
set to <option > syslog</option> or
<option > kmsg</option> .</para> </listitem>
</varlistentry>
<varlistentry >
<term > <varname > SyslogFacility=</varname> </term>
<listitem > <para > Sets the syslog
facility to use when logging to
syslog. One of <option > kern</option> ,
<option > user</option> ,
<option > mail</option> ,
<option > daemon</option> ,
<option > auth</option> ,
<option > syslog</option> ,
<option > lpr</option> ,
<option > news</option> ,
<option > uucp</option> ,
<option > cron</option> ,
<option > authpriv</option> ,
<option > ftp</option> ,
<option > local0</option> ,
<option > local1</option> ,
<option > local2</option> ,
<option > local3</option> ,
<option > local4</option> ,
<option > local5</option> ,
<option > local6</option> or
<option > local7</option> . See
<citerefentry > <refentrytitle > syslog</refentrytitle> <manvolnum > 3</manvolnum> </citerefentry>
for details. This option is only
useful when
<varname > StandardOutput=</varname> or
<varname > StandardError=</varname> are
set to <option > syslog</option> .
Defaults to
<option > daemon</option> .</para> </listitem>
</varlistentry>
<varlistentry >
<term > <varname > SyslogLevel=</varname> </term>
<listitem > <para > Default syslog level
to use when logging to syslog or the
kernel log buffer. One of
<option > emerg</option> ,
<option > alert</option> ,
<option > crit</option> ,
<option > err</option> ,
<option > warning</option> ,
<option > notice</option> ,
<option > info</option> ,
<option > debug</option> . See
<citerefentry > <refentrytitle > syslog</refentrytitle> <manvolnum > 3</manvolnum> </citerefentry>
for details. This option is only
useful when
<varname > StandardOutput=</varname> or
<varname > StandardError=</varname> are
set to <option > syslog</option> or
<option > kmsg</option> . Note that
individual lines output by the daemon
might be prefixed with a different log
level which can be used to override
the default log level specified
here. The interpretation of these
prefixes may be disabled with
2010-07-05 03:08:13 +04:00
<varname > SyslogLevelPrefix=</varname> ,
2010-07-03 01:24:38 +04:00
see below. For details see
2012-07-13 03:50:05 +04:00
<citerefentry > <refentrytitle > sd-daemon</refentrytitle> <manvolnum > 3</manvolnum> </citerefentry> .
2010-07-03 01:24:38 +04:00
Defaults to
<option > info</option> .</para> </listitem>
</varlistentry>
<varlistentry >
2010-07-05 03:08:13 +04:00
<term > <varname > SyslogLevelPrefix=</varname> </term>
2010-07-03 01:24:38 +04:00
<listitem > <para > Takes a boolean
2010-07-05 03:08:13 +04:00
argument. If true and
2010-07-03 01:24:38 +04:00
<varname > StandardOutput=</varname> or
<varname > StandardError=</varname> are
2012-10-26 03:07:07 +04:00
set to <option > syslog</option> ,
<option > kmsg</option> or
<option > journal</option> , log lines
2010-07-03 01:24:38 +04:00
written by the executed process that
are prefixed with a log level will be
passed on to syslog with this log
level set but the prefix removed. If
2010-07-05 03:08:13 +04:00
set to false, the interpretation of
2010-07-03 01:24:38 +04:00
these prefixes is disabled and the
logged lines are passed on as-is. For
details about this prefixing see
2012-07-13 03:50:05 +04:00
<citerefentry > <refentrytitle > sd-daemon</refentrytitle> <manvolnum > 3</manvolnum> </citerefentry> .
2010-07-05 03:08:13 +04:00
Defaults to true.</para> </listitem>
2010-07-03 01:24:38 +04:00
</varlistentry>
<varlistentry >
2010-07-04 23:12:10 +04:00
<term > <varname > TimerSlackNSec=</varname> </term>
2010-07-03 01:24:38 +04:00
<listitem > <para > Sets the timer slack
in nanoseconds for the executed
2012-05-31 06:27:03 +04:00
processes. The timer slack controls
the accuracy of wake-ups triggered by
2010-07-04 23:12:10 +04:00
timers. See
2010-07-03 01:24:38 +04:00
<citerefentry > <refentrytitle > prctl</refentrytitle> <manvolnum > 2</manvolnum> </citerefentry>
2010-07-04 23:12:10 +04:00
for more information. Note that in
contrast to most other time span
2010-11-11 16:24:47 +03:00
definitions this parameter takes an
2012-05-31 06:27:03 +04:00
integer value in nano-seconds if no
unit is specified. The usual time
units are understood
too.</para> </listitem>
2010-07-03 01:24:38 +04:00
</varlistentry>
<varlistentry >
<term > <varname > LimitCPU=</varname> </term>
<term > <varname > LimitFSIZE=</varname> </term>
<term > <varname > LimitDATA=</varname> </term>
<term > <varname > LimitSTACK=</varname> </term>
<term > <varname > LimitCORE=</varname> </term>
<term > <varname > LimitRSS=</varname> </term>
<term > <varname > LimitNOFILE=</varname> </term>
<term > <varname > LimitAS=</varname> </term>
<term > <varname > LimitNPROC=</varname> </term>
<term > <varname > LimitMEMLOCK=</varname> </term>
<term > <varname > LimitLOCKS=</varname> </term>
<term > <varname > LimitSIGPENDING=</varname> </term>
<term > <varname > LimitMSGQUEUE=</varname> </term>
<term > <varname > LimitNICE=</varname> </term>
<term > <varname > LimitRTPRIO=</varname> </term>
<term > <varname > LimitRTTIME=</varname> </term>
<listitem > <para > These settings control
various resource limits for executed
processes. See
<citerefentry > <refentrytitle > setrlimit</refentrytitle> <manvolnum > 2</manvolnum> </citerefentry>
2011-04-04 20:15:13 +04:00
for details. Use the string
<varname > infinity</varname> to
configure no limit on a specific
resource.</para> </listitem>
2010-07-03 01:24:38 +04:00
</varlistentry>
<varlistentry >
<term > <varname > PAMName=</varname> </term>
<listitem > <para > Sets the PAM service
name to set up a session as. If set
the executed process will be
registered as a PAM session under the
specified service name. This is only
useful in conjunction with the
<varname > User=</varname> setting. If
not set no PAM session will be opened
for the executed processes. See
<citerefentry > <refentrytitle > pam</refentrytitle> <manvolnum > 8</manvolnum> </citerefentry>
for details.</para> </listitem>
</varlistentry>
<varlistentry >
<term > <varname > TCPWrapName=</varname> </term>
<listitem > <para > If this is a
socket-activated service this sets the
tcpwrap service name to check the
permission for the current connection
with. This is only useful in
conjunction with socket-activated
services, and stream sockets (TCP) in
particular. It has no effect on other
2012-02-02 09:21:31 +04:00
socket types (e.g. datagram/UDP) and
on processes unrelated to socket-based
2010-07-03 01:24:38 +04:00
activation. If the tcpwrap
verification fails daemon start-up
will fail and the connection is
terminated. See
<citerefentry > <refentrytitle > tcpd</refentrytitle> <manvolnum > 8</manvolnum> </citerefentry>
2012-02-02 09:21:31 +04:00
for details. Note that this option may
be used to do access control checks
only. Shell commands and commands
described in
<citerefentry > <refentrytitle > hosts_options</refentrytitle> <manvolnum > 5</manvolnum> </citerefentry>
are not supported.</para> </listitem>
2010-07-03 01:24:38 +04:00
</varlistentry>
<varlistentry >
2011-03-18 05:13:15 +03:00
<term > <varname > CapabilityBoundingSet=</varname> </term>
<listitem > <para > Controls which
capabilities to include in the
capability bounding set for the
executed process. See
2010-07-03 01:24:38 +04:00
<citerefentry > <refentrytitle > capabilities</refentrytitle> <manvolnum > 7</manvolnum> </citerefentry>
2011-03-18 05:13:15 +03:00
for details. Takes a whitespace
2011-06-18 17:40:20 +04:00
separated list of capability names as
2011-03-18 05:13:15 +03:00
read by
2013-03-23 02:25:54 +04:00
<citerefentry > <refentrytitle > cap_from_name</refentrytitle> <manvolnum > 3</manvolnum> </citerefentry> ,
e.g. <literal > CAP_SYS_ADMIN
CAP_DAC_OVERRIDE
CAP_SYS_PTRACE</literal> .
2011-03-18 05:13:15 +03:00
Capabilities listed will be included
in the bounding set, all others are
removed. If the list of capabilities
2013-03-23 02:25:54 +04:00
is prefixed with <literal > ~</literal>
all but the listed capabilities will
be included, the effect of the
assignment inverted. Note that this
option also affects the respective
capabilities in the effective,
permitted and inheritable capability
sets, on top of what
<varname > Capabilities=</varname>
2012-05-24 06:00:56 +04:00
does. If this option is not used the
2011-03-18 05:13:15 +03:00
capability bounding set is not
modified on process execution, hence
no limits on the capabilities of the
2013-01-17 05:27:06 +04:00
process are enforced. This option may
appear more than once in which case
2013-03-23 02:25:54 +04:00
the bounding sets are merged. If the
empty string is assigned to this
option the bounding set is reset to
the empty capability set, and all
prior settings have no effect. If set
to <literal > ~</literal> (without any
further argument) the bounding set is
reset to the full set of available
capabilities, also undoing any
previous settings.</para> </listitem>
2010-07-03 01:24:38 +04:00
</varlistentry>
<varlistentry >
<term > <varname > SecureBits=</varname> </term>
<listitem > <para > Controls the secure
bits set for the executed process. See
<citerefentry > <refentrytitle > capabilities</refentrytitle> <manvolnum > 7</manvolnum> </citerefentry>
for details. Takes a list of strings:
<option > keep-caps</option> ,
<option > keep-caps-locked</option> ,
<option > no-setuid-fixup</option> ,
<option > no-setuid-fixup-locked</option> ,
2011-08-29 15:44:12 +04:00
<option > noroot</option> and/or
2013-01-17 05:27:06 +04:00
<option > noroot-locked</option> . This
option may appear more than once in
which case the secure bits are
ORed. If the empty string is assigned
to this option the bits are reset to
0.</para> </listitem>
2010-07-03 01:24:38 +04:00
</varlistentry>
<varlistentry >
2011-03-18 05:13:15 +03:00
<term > <varname > Capabilities=</varname> </term>
2010-07-03 01:24:38 +04:00
<listitem > <para > Controls the
<citerefentry > <refentrytitle > capabilities</refentrytitle> <manvolnum > 7</manvolnum> </citerefentry>
2011-03-18 05:13:15 +03:00
set for the executed process. Take a
capability string describing the
effective, permitted and inherited
capability sets as documented in
<citerefentry > <refentrytitle > cap_from_text</refentrytitle> <manvolnum > 3</manvolnum> </citerefentry> .
Note that these capability sets are
usually influenced by the capabilities
attached to the executed file. Due to
that
<varname > CapabilityBoundingSet=</varname>
is probably the much more useful
setting.</para> </listitem>
2010-07-03 01:24:38 +04:00
</varlistentry>
<varlistentry >
<term > <varname > ControlGroup=</varname> </term>
<listitem > <para > Controls the control
groups the executed processes shall be
2010-07-07 05:24:38 +04:00
made members of. Takes a
2010-09-03 18:30:48 +04:00
space-separated list of cgroup
2013-01-17 05:27:06 +04:00
identifiers. A cgroup identifier is
formatted like
2010-07-03 01:24:38 +04:00
<filename > cpu:/foo/bar</filename> ,
2013-01-17 05:27:06 +04:00
where "cpu" indicates the kernel
2010-07-03 01:24:38 +04:00
control group controller used, and
<filename > /foo/bar</filename> is the
2011-08-20 02:20:41 +04:00
control group path. The controller
name and ":" may be omitted in which
case the named systemd control group
2010-07-03 01:24:38 +04:00
hierarchy is implied. Alternatively,
the path and ":" may be omitted, in
which case the default control group
2013-01-17 05:27:06 +04:00
path for this unit is implied.</para>
<para > This option may be used to place
executed processes in arbitrary groups
in arbitrary hierarchies -- which may
then be externally configured with
additional execution limits. By
default systemd will place all
executed processes in separate
per-unit control groups (named after
the unit) in the systemd named
hierarchy. This option is primarily
intended to place executed processes
in specific paths in specific kernel
controller hierarchies. It is not
2011-08-20 02:20:41 +04:00
recommended to manipulate the service
control group path in the systemd
named hierarchy. For details about
control groups see <ulink
2013-01-17 05:27:06 +04:00
url="http://www.kernel.org/doc/Documentation/cgroups/cgroups.txt">cgroups.txt</ulink> .</para>
<para > This option may appear more than
once, in which case the list of
control group assignments is
merged. If the same hierarchy gets two
different paths assigned only the
later setting will take effect. If the
empty string is assigned to this
option the list of control group
assignments is reset, all previous
assignments will have no
effect.</para>
<para > Note that the list of control
group assignments of a unit is
extended implicitly based on the
settings of
<varname > DefaultControllers=</varname>
of
2013-02-11 23:42:24 +04:00
<citerefentry > <refentrytitle > systemd-system.conf</refentrytitle> <manvolnum > 5</manvolnum> </citerefentry> ,
2013-01-17 05:27:06 +04:00
but a unit's
<varname > ControlGroup=</varname>
setting for a specific controller
takes precedence.</para> </listitem>
2010-07-03 01:24:38 +04:00
</varlistentry>
2011-08-20 02:20:41 +04:00
<varlistentry >
<term > <varname > ControlGroupModify=</varname> </term>
<listitem > <para > Takes a boolean
argument. If true, the control groups
created for this unit will be owned by
the user specified with
<varname > User=</varname> (and the
appropriate group), and he/she can create
subgroups as well as add processes to
the group.</para> </listitem>
</varlistentry>
2012-01-18 18:40:21 +04:00
<varlistentry >
2012-01-19 00:47:30 +04:00
<term > <varname > ControlGroupPersistent=</varname> </term>
2012-01-18 18:40:21 +04:00
<listitem > <para > Takes a boolean
argument. If true, the control groups
created for this unit will be marked
2012-01-19 00:47:30 +04:00
to be persistent, i.e. systemd will
2012-01-18 18:40:21 +04:00
not remove them when stopping the
unit. The default is false, meaning
that the control groups will be
removed when the unit is stopped. For
details about the semantics of this
logic see <ulink
url="http://www.freedesktop.org/wiki/Software/systemd/PaxControlGroups">PaxControlGroups</ulink> .</para> </listitem>
</varlistentry>
2011-08-20 02:20:41 +04:00
<varlistentry >
<term > <varname > ControlGroupAttribute=</varname> </term>
<listitem > <para > Set a specific control
group attribute for executed
2012-09-04 21:24:16 +04:00
processes, and (if needed) add the
2011-08-20 02:20:41 +04:00
executed processes to a cgroup in the
hierarchy of the controller the
attribute belongs to. Takes two
space-separated arguments: the
attribute name (syntax is
<literal > cpu.shares</literal> where
<literal > cpu</literal> refers to a
specific controller and
<literal > shares</literal> to the
attribute name), and the attribute
value. Example:
<literal > ControlGroupAttribute=cpu.shares
512</literal> . If this option is used
for an attribute that belongs to a
kernel controller hierarchy the unit
is not already configured to be added
to (for example via the
<literal > ControlGroup=</literal>
option) then the unit will be added to
the controller and the default unit
cgroup path is implied. Thus, using
<varname > ControlGroupAttribute=</varname>
2013-01-17 05:27:06 +04:00
is in most cases sufficient to make
use of control group enforcements,
2011-08-20 02:20:41 +04:00
explicit
<varname > ControlGroup=</varname> are
only necessary in case the implied
default control group path for a
service is not desirable. For details
about control group attributes see
<ulink
url="http://www.kernel.org/doc/Documentation/cgroups/cgroups.txt">cgroups.txt</ulink> . This
option may appear more than once, in
order to set multiple control group
2013-01-17 05:27:06 +04:00
attributes. If this option is used
multiple times for the same cgroup
attribute only the later setting takes
effect. If the empty string is
assigned to this option the list of
attributes is reset, all previous
cgroup attribute settings have no
effect, including those done with
<varname > CPUShares=</varname> ,
<varname > MemoryLimit=</varname> ,
<varname > MemorySoftLimit</varname> ,
<varname > DeviceAllow=</varname> ,
<varname > DeviceDeny=</varname> ,
<varname > BlockIOWeight=</varname> ,
<varname > BlockIOReadBandwidth=</varname> ,
<varname > BlockIOWriteBandwidth=</varname> .
</para> </listitem>
2011-08-20 02:20:41 +04:00
</varlistentry>
<varlistentry >
<term > <varname > CPUShares=</varname> </term>
<listitem > <para > Assign the specified
2011-08-20 03:38:10 +04:00
overall CPU time shares to the
processes executed. Takes an integer
value. This controls the
2011-08-20 02:20:41 +04:00
<literal > cpu.shares</literal> control
2011-08-20 03:38:10 +04:00
group attribute, which defaults to
1024. For details about this control
group attribute see <ulink
2011-08-20 02:20:41 +04:00
url="http://www.kernel.org/doc/Documentation/scheduler/sched-design-CFS.txt">sched-design-CFS.txt</ulink> .</para> </listitem>
</varlistentry>
<varlistentry >
<term > <varname > MemoryLimit=</varname> </term>
<term > <varname > MemorySoftLimit=</varname> </term>
<listitem > <para > Limit the overall memory usage
of the executed processes to a certain
size. Takes a memory size in bytes. If
the value is suffixed with K, M, G or
T the specified memory size is parsed
2011-08-20 03:38:10 +04:00
as Kilobytes, Megabytes, Gigabytes,
Reword sentences that contain psuedo-English "resp."
As you likely know, Arch Linux is in the process of moving to systemd.
So I was reading through the various systemd docs and quickly became
baffled by this new abbreviation "resp.", which I've never seen before
in my English-mother-tongue life.
Some quick Googling turned up a reference:
<http://www.transblawg.eu/index.php?/archives/870-Resp.-and-other-non-existent-English-wordsNicht-existente-englische-Woerter.html>
I guess it's a literal translation of the German "Beziehungsweise", but
English doesn't work the same way. The word "respectively" is used
exclusively to provide an ordering connection between two lists. E.g.
"the prefixes k, M, and G refer to kilo-, mega-, and giga-,
respectively." It is also never abbreviated to "resp." So the sentence
"Sets the default output resp. error output for all services and
sockets" makes no sense to a natural English speaker.
This patch removes all instances of "resp." in the man pages and
replaces them with sentences which are much more clear and, hopefully,
grammatically valid. In almost all instances, it was simply replacing
"resp." with "or," which the original author (Lennart?) could probably
just do in the future.
The only other instances of "resp." are in the src/ subtree, which I
don't feel privileged to correct.
Signed-off-by: Andrew Eikum <aeikum@codeweavers.com>
2012-10-15 22:59:12 +04:00
or Terabytes (to the base
1024), respectively. This controls the
2011-08-20 02:20:41 +04:00
<literal > memory.limit_in_bytes</literal>
and
<literal > memory.soft_limit_in_bytes</literal>
control group attributes. For details
about these control group attributes
see <ulink
url="http://www.kernel.org/doc/Documentation/cgroups/memory.txt">memory.txt</ulink> .</para> </listitem>
</varlistentry>
<varlistentry >
<term > <varname > DeviceAllow=</varname> </term>
<term > <varname > DeviceDeny=</varname> </term>
<listitem > <para > Control access to
specific device nodes by the executed processes. Takes two
space separated strings: a device node
path (such as
<filename > /dev/null</filename> )
followed by a combination of r, w, m
Reword sentences that contain psuedo-English "resp."
As you likely know, Arch Linux is in the process of moving to systemd.
So I was reading through the various systemd docs and quickly became
baffled by this new abbreviation "resp.", which I've never seen before
in my English-mother-tongue life.
Some quick Googling turned up a reference:
<http://www.transblawg.eu/index.php?/archives/870-Resp.-and-other-non-existent-English-wordsNicht-existente-englische-Woerter.html>
I guess it's a literal translation of the German "Beziehungsweise", but
English doesn't work the same way. The word "respectively" is used
exclusively to provide an ordering connection between two lists. E.g.
"the prefixes k, M, and G refer to kilo-, mega-, and giga-,
respectively." It is also never abbreviated to "resp." So the sentence
"Sets the default output resp. error output for all services and
sockets" makes no sense to a natural English speaker.
This patch removes all instances of "resp." in the man pages and
replaces them with sentences which are much more clear and, hopefully,
grammatically valid. In almost all instances, it was simply replacing
"resp." with "or," which the original author (Lennart?) could probably
just do in the future.
The only other instances of "resp." are in the src/ subtree, which I
don't feel privileged to correct.
Signed-off-by: Andrew Eikum <aeikum@codeweavers.com>
2012-10-15 22:59:12 +04:00
to control reading, writing, or
2011-08-20 02:20:41 +04:00
creating of the specific device node
Reword sentences that contain psuedo-English "resp."
As you likely know, Arch Linux is in the process of moving to systemd.
So I was reading through the various systemd docs and quickly became
baffled by this new abbreviation "resp.", which I've never seen before
in my English-mother-tongue life.
Some quick Googling turned up a reference:
<http://www.transblawg.eu/index.php?/archives/870-Resp.-and-other-non-existent-English-wordsNicht-existente-englische-Woerter.html>
I guess it's a literal translation of the German "Beziehungsweise", but
English doesn't work the same way. The word "respectively" is used
exclusively to provide an ordering connection between two lists. E.g.
"the prefixes k, M, and G refer to kilo-, mega-, and giga-,
respectively." It is also never abbreviated to "resp." So the sentence
"Sets the default output resp. error output for all services and
sockets" makes no sense to a natural English speaker.
This patch removes all instances of "resp." in the man pages and
replaces them with sentences which are much more clear and, hopefully,
grammatically valid. In almost all instances, it was simply replacing
"resp." with "or," which the original author (Lennart?) could probably
just do in the future.
The only other instances of "resp." are in the src/ subtree, which I
don't feel privileged to correct.
Signed-off-by: Andrew Eikum <aeikum@codeweavers.com>
2012-10-15 22:59:12 +04:00
by the unit, respectively. This controls the
2011-08-20 02:20:41 +04:00
<literal > devices.allow</literal>
and
<literal > devices.deny</literal>
control group attributes. For details
about these control group attributes
see <ulink
url="http://www.kernel.org/doc/Documentation/cgroups/devices.txt">devices.txt</ulink> .</para> </listitem>
</varlistentry>
2011-08-20 03:38:10 +04:00
<varlistentry >
<term > <varname > BlockIOWeight=</varname> </term>
<listitem > <para > Set the default or
per-device overall block IO weight
value for the executed
processes. Takes either a single
weight value (between 10 and 1000) to
set the default block IO weight, or a
2011-08-21 02:28:30 +04:00
space separated pair of a file path
and a weight value to specify the
2011-08-20 03:38:10 +04:00
device specific weight value (Example:
2011-08-21 02:28:30 +04:00
"/dev/sda 500"). The file path may be
specified as path to a block device
node or as any other file in which
case the backing block device of the
file system of the file is
determined. This controls the
2011-08-20 03:38:10 +04:00
<literal > blkio.weight</literal> and
<literal > blkio.weight_device</literal>
control group attributes, which
default to 1000. Use this option
multiple times to set weights for
multiple devices. For details about
these control group attributes see
<ulink
url="http://www.kernel.org/doc/Documentation/cgroups/blkio-controller.txt">blkio-controller.txt</ulink> .</para> </listitem>
</varlistentry>
<varlistentry >
<term > <varname > BlockIOReadBandwidth=</varname> </term>
<term > <varname > BlockIOWriteBandwidth=</varname> </term>
<listitem > <para > Set the per-device
2012-07-15 12:41:40 +04:00
overall block IO bandwidth limit for
2011-08-21 02:28:30 +04:00
the executed processes. Takes a space
separated pair of a file path and a
2012-07-15 12:41:40 +04:00
bandwidth value (in bytes per second)
2011-08-21 02:28:30 +04:00
to specify the device specific
bandwidth. The file path may be
specified as path to a block device
node or as any other file in which
case the backing block device of the
file system of the file is determined.
2012-07-15 12:41:40 +04:00
If the bandwidth is suffixed with K, M,
G, or T the specified bandwidth is
2011-08-21 02:28:30 +04:00
parsed as Kilobytes, Megabytes,
Reword sentences that contain psuedo-English "resp."
As you likely know, Arch Linux is in the process of moving to systemd.
So I was reading through the various systemd docs and quickly became
baffled by this new abbreviation "resp.", which I've never seen before
in my English-mother-tongue life.
Some quick Googling turned up a reference:
<http://www.transblawg.eu/index.php?/archives/870-Resp.-and-other-non-existent-English-wordsNicht-existente-englische-Woerter.html>
I guess it's a literal translation of the German "Beziehungsweise", but
English doesn't work the same way. The word "respectively" is used
exclusively to provide an ordering connection between two lists. E.g.
"the prefixes k, M, and G refer to kilo-, mega-, and giga-,
respectively." It is also never abbreviated to "resp." So the sentence
"Sets the default output resp. error output for all services and
sockets" makes no sense to a natural English speaker.
This patch removes all instances of "resp." in the man pages and
replaces them with sentences which are much more clear and, hopefully,
grammatically valid. In almost all instances, it was simply replacing
"resp." with "or," which the original author (Lennart?) could probably
just do in the future.
The only other instances of "resp." are in the src/ subtree, which I
don't feel privileged to correct.
Signed-off-by: Andrew Eikum <aeikum@codeweavers.com>
2012-10-15 22:59:12 +04:00
Gigabytes, or Terabytes, respectively (Example:
2011-08-21 02:28:30 +04:00
"/dev/disk/by-path/pci-0000:00:1f.2-scsi-0:0:0:0
5M"). This controls the
2011-08-20 03:38:10 +04:00
<literal > blkio.read_bps_device</literal>
and
<literal > blkio.write_bps_device</literal>
control group attributes. Use this
2012-07-15 12:41:40 +04:00
option multiple times to set bandwidth
2011-08-20 03:38:10 +04:00
limits for multiple devices. For
details about these control group
attributes see <ulink
url="http://www.kernel.org/doc/Documentation/cgroups/blkio-controller.txt">blkio-controller.txt</ulink> .</para> </listitem>
</varlistentry>
2010-07-03 01:24:38 +04:00
<varlistentry >
<term > <varname > ReadWriteDirectories=</varname> </term>
<term > <varname > ReadOnlyDirectories=</varname> </term>
<term > <varname > InaccessibleDirectories=</varname> </term>
<listitem > <para > Sets up a new
file-system name space for executed
processes. These options may be used
to limit access a process might have
to the main file-system
hierarchy. Each setting takes a
2010-09-03 18:30:48 +04:00
space-separated list of absolute
2010-07-03 01:24:38 +04:00
directory paths. Directories listed in
<varname > ReadWriteDirectories=</varname>
are accessible from within the
namespace with the same access rights
as from outside. Directories listed in
<varname > ReadOnlyDirectories=</varname>
are accessible for reading only,
writing will be refused even if the
usual file access controls would
permit this. Directories listed in
<varname > InaccessibleDirectories=</varname>
2013-01-17 05:27:06 +04:00
will be made inaccessible for
processes inside the namespace. Note
that restricting access with these
options does not extend to submounts
of a directory. You must list
submounts separately in these settings
to ensure the same limited
access. These options may be specified
more than once in which case all
directories listed will have limited
access from within the namespace. If
the empty string is assigned to this
option the specific list is reset, and
all prior assignments have no
effect.</para> </listitem>
2010-07-03 01:24:38 +04:00
</varlistentry>
<varlistentry >
<term > <varname > PrivateTmp=</varname> </term>
<listitem > <para > Takes a boolean
2011-08-02 07:24:58 +04:00
argument. If true sets up a new file
system namespace for the executed
2013-01-25 23:25:43 +04:00
processes and mounts private
<filename > /tmp</filename> and
<filename > /var/tmp</filename> directories
inside it, that are not shared by
2010-07-03 01:24:38 +04:00
processes outside of the
namespace. This is useful to secure
access to temporary files of the
process, but makes sharing between
processes via
2013-01-25 23:25:43 +04:00
<filename > /tmp</filename> or
<filename > /var/tmp</filename>
2013-03-14 21:12:27 +04:00
impossible. All temporary data created
by service will be removed after service
is stopped. Defaults to
2011-08-02 07:24:58 +04:00
false.</para> </listitem>
</varlistentry>
<varlistentry >
<term > <varname > PrivateNetwork=</varname> </term>
<listitem > <para > Takes a boolean
argument. If true sets up a new
network namespace for the executed
processes and configures only the
loopback network device
<literal > lo</literal> inside it. No
other network devices will be
available to the executed process.
This is useful to securely turn off
network access by the executed
process. Defaults to
false.</para> </listitem>
2010-07-03 01:24:38 +04:00
</varlistentry>
<varlistentry >
<term > <varname > MountFlags=</varname> </term>
<listitem > <para > Takes a mount
propagation flag:
<option > shared</option> ,
<option > slave</option> or
<option > private</option> , which
2012-08-13 17:27:04 +04:00
control whether the file system
namespace set up for this unit's
processes will receive or propagate
new mounts. See
2012-11-27 14:40:08 +04:00
<citerefentry > <refentrytitle > mount</refentrytitle> <manvolnum > 2</manvolnum> </citerefentry>
2012-08-13 17:27:04 +04:00
for details. Default to
<option > shared</option> .</para> </listitem>
2010-07-03 01:24:38 +04:00
</varlistentry>
2010-10-08 18:06:23 +04:00
<varlistentry >
<term > <varname > UtmpIdentifier=</varname> </term>
2012-09-04 21:24:16 +04:00
<listitem > <para > Takes a four
2010-10-08 18:06:23 +04:00
character identifier string for an
utmp/wtmp entry for this service. This
should only be set for services such
as <command > getty</command>
implementations where utmp/wtmp
entries must be created and cleared
before and after execution. If the
configured string is longer than four
characters it is truncated and the
terminal four characters are
used. This setting interprets %I style
string replacements. This setting is
unset by default, i.e. no utmp/wtmp
entries are created or cleaned up for
this service.</para> </listitem>
</varlistentry>
2012-02-09 06:18:04 +04:00
<varlistentry >
<term > <varname > IgnoreSIGPIPE=</varname> </term>
<listitem > <para > Takes a boolean
argument. If true causes SIGPIPE to be
ignored in the executed
process. Defaults to true, since
SIGPIPE generally is useful only in
shell pipelines.</para> </listitem>
</varlistentry>
2012-07-17 06:17:53 +04:00
<varlistentry >
<term > <varname > NoNewPrivileges=</varname> </term>
<listitem > <para > Takes a boolean
argument. If true ensures that the
service process and all its children
can never gain new privileges. This
option is more powerful than the respective
secure bits flags (see above), as it
also prohibits UID changes of any
kind. This is the simplest, most
effective way to ensure that a process
and its children can never elevate
privileges again.</para> </listitem>
</varlistentry>
<varlistentry >
<term > <varname > SystemCallFilter=</varname> </term>
<listitem > <para > Takes a space
separated list of system call
names. If this setting is used all
system calls executed by the unit
process except for the listed ones
will result in immediate process
termination with the SIGSYS signal
(whitelisting). If the first character
of the list is <literal > ~</literal>
the effect is inverted: only the
listed system calls will result in
immediate process termination
(blacklisting). If this option is used
<varname > NoNewPrivileges=yes</varname>
is implied. This feature makes use of
the Secure Computing Mode 2 interfaces
of the kernel ('seccomp filtering')
and is useful for enforcing a minimal
sandboxing environment. Note that the
<function > execve</function> ,
<function > rt_sigreturn</function> ,
<function > sigreturn</function> ,
<function > exit_group</function> ,
<function > exit</function> system calls
are implicitly whitelisted and don't
2013-01-17 05:27:06 +04:00
need to be listed explicitly. This
option may be specified more than once
in which case the filter masks are
merged. If the empty string is
assigned the filter is reset, all
prior assignments will have no
effect.</para> </listitem>
2012-07-17 06:17:53 +04:00
</varlistentry>
2010-07-03 01:24:38 +04:00
</variablelist>
</refsect1>
<refsect1 >
<title > See Also</title>
<para >
2010-07-07 03:38:56 +04:00
<citerefentry > <refentrytitle > systemd</refentrytitle> <manvolnum > 1</manvolnum> </citerefentry> ,
2010-07-03 01:24:38 +04:00
<citerefentry > <refentrytitle > systemctl</refentrytitle> <manvolnum > 8</manvolnum> </citerefentry> ,
2012-03-26 22:58:47 +04:00
<citerefentry > <refentrytitle > journalctl</refentrytitle> <manvolnum > 8</manvolnum> </citerefentry> ,
2010-07-03 01:24:38 +04:00
<citerefentry > <refentrytitle > systemd.unit</refentrytitle> <manvolnum > 5</manvolnum> </citerefentry> ,
<citerefentry > <refentrytitle > systemd.service</refentrytitle> <manvolnum > 5</manvolnum> </citerefentry> ,
<citerefentry > <refentrytitle > systemd.socket</refentrytitle> <manvolnum > 5</manvolnum> </citerefentry> ,
2011-01-18 02:40:10 +03:00
<citerefentry > <refentrytitle > systemd.swap</refentrytitle> <manvolnum > 5</manvolnum> </citerefentry> ,
2012-07-20 01:47:10 +04:00
<citerefentry > <refentrytitle > systemd.mount</refentrytitle> <manvolnum > 5</manvolnum> </citerefentry> ,
2013-01-15 07:08:33 +04:00
<citerefentry > <refentrytitle > systemd.kill</refentrytitle> <manvolnum > 5</manvolnum> </citerefentry> ,
<citerefentry > <refentrytitle > systemd.directives</refentrytitle> <manvolnum > 7</manvolnum> </citerefentry>
2010-07-03 01:24:38 +04:00
</para>
</refsect1>
</refentry>
