2N/A<?xml version='1.0'?> <!--*-nxml-*-->

2N/A<?xml-stylesheet type="text/xsl" href="http://docbook.sourceforge.net/release/xsl/current/xhtml/docbook.xsl"?>

2N/A<!DOCTYPE refentry PUBLIC "-//OASIS//DTD DocBook XML V4.2//EN"

2N/A "http://www.oasis-open.org/docbook/xml/4.2/docbookx.dtd">

2N/A

2N/A

2N/A<refentry id="systemd.exec">

2N/A <refentryinfo>

2N/A <title>systemd.exec</title>

2N/A <productname>systemd</productname>

2N/A

2N/A <authorgroup>

2N/A <author>

12N/A <contrib>Developer</contrib>

12N/A <firstname>Lennart</firstname>

2N/A <surname>Poettering</surname>

2N/A <email>lennart@poettering.net</email>

2N/A </author>

2N/A </authorgroup>

26N/A </refentryinfo>

26N/A

2N/A <refmeta>

26N/A <refentrytitle>systemd.exec</refentrytitle>

38N/A <manvolnum>5</manvolnum>

26N/A </refmeta>

26N/A

26N/A <refnamediv>

26N/A <refname>systemd.exec</refname>

26N/A <refpurpose>systemd execution environment configuration</refpurpose>

26N/A </refnamediv>

26N/A

26N/A <refsynopsisdiv>

26N/A <para><filename>systemd.service</filename>,

26N/A <filename>systemd.socket</filename>,

26N/A <filename>systemd.mount</filename>,

26N/A <filename>systemd.swap</filename></para>

26N/A </refsynopsisdiv>

26N/A

26N/A <refsect1>

26N/A <title>Description</title>

26N/A

26N/A <para>Unit configuration files for services, sockets

26N/A mount points and swap devices share a subset of

26N/A configuration options which define the execution

2N/A environment of spawned processes.</para>

26N/A

26N/A <para>This man page lists the configuration options

26N/A shared by these three unit types. See

26N/A <citerefentry><refentrytitle>systemd.unit</refentrytitle><manvolnum>5</manvolnum></citerefentry>

26N/A for the common options of all unit configuration

26N/A files, and

26N/A <citerefentry><refentrytitle>systemd.service</refentrytitle><manvolnum>5</manvolnum></citerefentry>,

26N/A <citerefentry><refentrytitle>systemd.socket</refentrytitle><manvolnum>5</manvolnum></citerefentry>,

26N/A <citerefentry><refentrytitle>systemd.swap</refentrytitle><manvolnum>5</manvolnum></citerefentry>

26N/A and

26N/A <citerefentry><refentrytitle>systemd.mount</refentrytitle><manvolnum>5</manvolnum></citerefentry>

26N/A for more information on the specific unit

26N/A configuration files. The execution specific

2N/A configuration options are configured in the [Service],

26N/A [Socket], [Mount] resp. [Swap] section, depending on the unit

26N/A type.</para>

27N/A </refsect1>

27N/A

27N/A <refsect1>

26N/A <title>Options</title>

26N/A

12N/A <variablelist>

30N/A

26N/A <varlistentry>

26N/A <term><varname>WorkingDirectory=</varname></term>

26N/A

2N/A <listitem><para>Takes an absolute

26N/A directory path. Sets the working

30N/A directory for executed

26N/A processes.</para></listitem>

2N/A </varlistentry>

7N/A

27N/A <varlistentry>

27N/A <term><varname>RootDirectory=</varname></term>

27N/A

38N/A <listitem><para>Takes an absolute

38N/A directory path. Sets the root

38N/A directory for executed processes, with

21N/A the

7N/A <citerefentry><refentrytitle>chroot</refentrytitle><manvolnum>2</manvolnum></citerefentry>

26N/A system call. If this is used it must

26N/A be ensured that the process and all

38N/A its auxiliary files are available in

26N/A the <function>chroot()</function>

26N/A jail.</para></listitem>

26N/A </varlistentry>

30N/A

26N/A <varlistentry>

46N/A <term><varname>User=</varname></term>

46N/A <term><varname>Group=</varname></term>

46N/A

26N/A <listitem><para>Sets the Unix user

26N/A resp. group the processes are executed

46N/A as. Takes a single user resp. group

46N/A name or ID as argument. If no group is

46N/A set the default group of the user is

2N/A chosen.</para></listitem>

46N/A </varlistentry>

53N/A

53N/A <varlistentry>

46N/A <term><varname>SupplementaryGroups=</varname></term>

46N/A

26N/A <listitem><para>Sets the supplementary

46N/A Unix groups the processes are executed

46N/A as. This takes a space separated list

46N/A of group names or IDs. This option may

53N/A be specified more than once in which

26N/A case all listed groups are set as

46N/A supplementary groups. This option does

46N/A not override but extends the list of

46N/A supplementary groups configured in the

53N/A system group database for the

46N/A user.</para></listitem>

53N/A </varlistentry>

53N/A

2N/A <varlistentry>

46N/A <term><varname>Nice=</varname></term>

38N/A

46N/A <listitem><para>Sets the default nice

53N/A level (scheduling priority) for

53N/A executed processes. Takes an integer

53N/A between -20 (highest priority) and 19

46N/A (lowest priority). See

38N/A <citerefentry><refentrytitle>setpriority</refentrytitle><manvolnum>2</manvolnum></citerefentry>

46N/A for details.</para></listitem>

46N/A </varlistentry>

26N/A

48N/A <varlistentry>

46N/A <term><varname>OOMScoreAdjust=</varname></term>

2N/A

38N/A <listitem><para>Sets the adjustment

26N/A level for the Out-Of-Memory killer for

2N/A executed processes. Takes an integer

32N/A between -1000 (to disable OOM killing

32N/A for this process) and 1000 (to make

32N/A killing of this process under memory

32N/A pressure very likely). See <ulink

32N/A url="http://www.kernel.org/doc/Documentation/filesystems/proc.txt">proc.txt</ulink>

32N/A for details.</para></listitem>

32N/A </varlistentry>

32N/A

32N/A <varlistentry>

32N/A <term><varname>IOSchedulingClass=</varname></term>

38N/A

38N/A <listitem><para>Sets the IO scheduling

38N/A class for executed processes. Takes an

38N/A integer between 0 and 3 or one of the

38N/A strings <option>none</option>,

38N/A <option>realtime</option>,

38N/A <option>best-effort</option> or

38N/A <option>idle</option>. See

38N/A <citerefentry><refentrytitle>ioprio_set</refentrytitle><manvolnum>2</manvolnum></citerefentry>

38N/A for details.</para></listitem>

38N/A </varlistentry>

38N/A

38N/A <varlistentry>

26N/A <term><varname>IOSchedulingPriority=</varname></term>

26N/A

26N/A <listitem><para>Sets the IO scheduling

26N/A priority for executed processes. Takes

26N/A an integer between 0 (highest

26N/A priority) and 7 (lowest priority). The

26N/A available priorities depend on the

26N/A selected IO scheduling class (see

26N/A above). See

32N/A <citerefentry><refentrytitle>ioprio_set</refentrytitle><manvolnum>2</manvolnum></citerefentry>

32N/A for details.</para></listitem>

32N/A </varlistentry>

32N/A

32N/A <varlistentry>

32N/A <term><varname>CPUSchedulingPolicy=</varname></term>

32N/A

32N/A <listitem><para>Sets the CPU

38N/A scheduling policy for executed

38N/A processes. Takes one of

38N/A <option>other</option>,

32N/A <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

processes. Takes an integer between 1

(lowest priority) and 99 (highest

priority). The available priority

range depends on the selected CPU

scheduling policy (see above). See

<citerefentry><refentrytitle>sched_setscheduler</refentrytitle><manvolnum>2</manvolnum></citerefentry>

for details.</para></listitem>

</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

processes. Takes a space-separated

list of CPU indexes. See

<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

0002.</para></listitem>

</varlistentry>

<varlistentry>

<term><varname>Environment=</varname></term>

<listitem><para>Sets environment

variables for executed

processes. Takes a space-separated

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

override the earlier setting. See

<citerefentry><refentrytitle>environ</refentrytitle><manvolnum>7</manvolnum></citerefentry>

for details.</para></listitem>

</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

contain new-line separated variable

assignments. Empty lines and lines

starting with ; or # will be ignored,

which may be used for commenting. The

argument passed should be an absolute

file name, optionally prefixed with

"-", which indicates that if the file

does not exist it won't be read and no

error or warning message is

logged. The files listed with this

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

earlier setting. </para></listitem>

</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

being controlled by another process the

executed process waits until the current

controlling process releases the

terminal.

<option>tty-force</option>

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>,

<option>kmsg</option>,

<option>kmsg+console</option>,

<option>syslog+console</option> or

<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>

system logger. <option>kmsg</option>

connects it with the kernel log buffer

which is accessible via

<citerefentry><refentrytitle>dmesg</refentrytitle><manvolnum>1</manvolnum></citerefentry>. <option>syslog+console</option>

and <option>kmsg+console</option> work

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

similar to the respective option of

<varname>StandardInput=</varname>.

This setting defaults to

<option>inherit</option>.</para></listitem>

</varlistentry>

<varlistentry>

<term><varname>StandardError=</varname></term>

<listitem><para>Controls where file

descriptor 2 (STDERR) of the executed

processes is connected to. The

available options are identical to

those of

<varname>StandardOutput=</varname>,

with one exception: if set to

<option>inherit</option> the file

descriptor used for standard output is

duplicated for standard error. This

setting defaults to

<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>

<varlistentry>

<term><varname>SyslogIdentifier=</varname></term>

<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

<varname>SyslogLevelPrefix=</varname>,

see below. For details see

<citerefentry><refentrytitle>sd-daemon</refentrytitle><manvolnum>7</manvolnum></citerefentry>.

Defaults to

<option>info</option>.</para></listitem>

</varlistentry>

<varlistentry>

<term><varname>SyslogLevelPrefix=</varname></term>

<listitem><para>Takes a boolean

argument. If true and

<varname>StandardOutput=</varname> or

<varname>StandardError=</varname> are

set to <option>syslog</option> or

<option>kmsg</option> log lines

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

set to false, the interpretation of

these prefixes is disabled and the

logged lines are passed on as-is. For

details about this prefixing see

<citerefentry><refentrytitle>sd-daemon</refentrytitle><manvolnum>7</manvolnum></citerefentry>.

Defaults to true.</para></listitem>

</varlistentry>

<varlistentry>

<term><varname>TimerSlackNSec=</varname></term>

<listitem><para>Sets the timer slack

in nanoseconds for the executed

processes. The timer slack controls the

accuracy of wake-ups triggered by

timers. See

<citerefentry><refentrytitle>prctl</refentrytitle><manvolnum>2</manvolnum></citerefentry>

for more information. Note that in

contrast to most other time span

definitions this parameter takes an

integer value in nano-seconds and does

not understand any other

units.</para></listitem>

</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>

for details.</para></listitem>

</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

socket types (e.g. datagram/UDP) and on processes

unrelated to socket-based

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>

for details.</para></listitem>

</varlistentry>

<varlistentry>

<term><varname>CapabilityBoundingSet=</varname></term>

<listitem><para>Controls which

capabilities to include in the

capability bounding set for the

executed process. See

<citerefentry><refentrytitle>capabilities</refentrytitle><manvolnum>7</manvolnum></citerefentry>

for details. Takes a whitespace

seperated list of capability names as

read by

<citerefentry><refentrytitle>cap_from_name</refentrytitle><manvolnum>3</manvolnum></citerefentry>.

Capabilities listed will be included

in the bounding set, all others are

removed. If the list of capabilities

is prefixed with ~ all but the listed

capabilities will be included, the

effect of this assignment

inverted. Note that this option does

not actually set or unset any

capabilities in the effective,

permitted or inherited capability

sets. That's what

<varname>Capabilities=</varname> is

for. If this option is not used the

capability bounding set is not

modified on process execution, hence

no limits on the capabilities of the

process are enforced.</para></listitem>

</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>,

<option>no-setuid-noroot</option> and/or

<option>no-setuid-noroot-locked</option>.

</para></listitem>

</varlistentry>

<varlistentry>

<term><varname>Capabilities=</varname></term>

<listitem><para>Controls the

<citerefentry><refentrytitle>capabilities</refentrytitle><manvolnum>7</manvolnum></citerefentry>

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>

</varlistentry>

<varlistentry>

<term><varname>ControlGroup=</varname></term>

<listitem><para>Controls the control

groups the executed processes shall be

made members of. Takes a

space-separated list of cgroup

identifiers. A cgroup identifier has a

format like

<filename>cpu:/foo/bar</filename>,

where "cpu" identifies the kernel

control group controller used, and

<filename>/foo/bar</filename> is the

control group path. The controller name

and ":" may be omitted in which case

the named systemd control group

hierarchy is implied. Alternatively,

the path and ":" may be omitted, in

which case the default control group

path for this unit is implied. This

option may be used to place executed

processes in arbitrary groups in

arbitrary hierachies -- which can be

configured externally 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. Since every

process can be in one group per

hierarchy only overriding the control group

path in the named systemd hierarchy

will disable automatic placement in

the default group. For details about control

groups see <ulink

url="http://www.kernel.org/doc/Documentation/cgroups/cgroups.txt">cgroups.txt</ulink>.</para></listitem>

</varlistentry>

<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

space-separated list of absolute

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>

will be made inaccesible 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.</para></listitem>

</varlistentry>

<varlistentry>

<term><varname>PrivateTmp=</varname></term>

<listitem><para>Takes a boolean

argument. If true sets up a new

namespace for the executed processes

and mounts a private

<filename>/tmp</filename> directory

inside it, that is not shared by

processes outside of the

namespace. This is useful to secure

access to temporary files of the

process, but makes sharing between

processes via

<filename>/tmp</filename>

impossible. Defaults to false.</para></listitem>

</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

control whether namespaces set up with

<varname>ReadWriteDirectories=</varname>,

<varname>ReadOnlyDirectories=</varname>

and

<varname>InaccessibleDirectories=</varname>

receive or propagate new mounts

from/to the main namespace. See

<citerefentry><refentrytitle>mount</refentrytitle><manvolnum>1</manvolnum></citerefentry>

for details. Defaults to

<option>shared</option>, i.e. the new

namespace will both receive new mount

points from the main namespace as well

as propagate new mounts to

it.</para></listitem>

</varlistentry>

<varlistentry>

<term><varname>UtmpIdentifier=</varname></term>

<listitem><para>Takes a a four

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>

</variablelist>

</refsect1>

<refsect1>

<title>See Also</title>

<para>

<citerefentry><refentrytitle>systemd</refentrytitle><manvolnum>1</manvolnum></citerefentry>,

<citerefentry><refentrytitle>systemctl</refentrytitle><manvolnum>8</manvolnum></citerefentry>,

<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>,

<citerefentry><refentrytitle>systemd.swap</refentrytitle><manvolnum>5</manvolnum></citerefentry>,

<citerefentry><refentrytitle>systemd.mount</refentrytitle><manvolnum>5</manvolnum></citerefentry>

</para>

</refsect1>

</refentry>