man: document that inability to execute Symlinks= is not fatal

Fixes: #6920
This commit is contained in:
Lennart Poettering 2017-09-26 18:36:41 +02:00
parent 1af87ab7d6
commit 3ecc7fc3e6
1 changed files with 7 additions and 8 deletions

View File

@ -804,14 +804,13 @@
<varlistentry>
<term><varname>Symlinks=</varname></term>
<listitem><para>Takes a list of file system paths. The
specified paths will be created as symlinks to the AF_UNIX
socket path or FIFO path of this socket unit. If this setting
is used, only one AF_UNIX socket in the file system or one
FIFO may be configured for the socket unit. Use this option to
manage one or more symlinked alias names for a socket, binding
their lifecycle together. If the empty string is assigned, the
list of paths is reset. Defaults to the empty list.</para></listitem>
<listitem><para>Takes a list of file system paths. The specified paths will be created as symlinks to the
<constant>AF_UNIX</constant> socket path or FIFO path of this socket unit. If this setting is used, only one
<constant>AF_UNIX</constant> socket in the file system or one FIFO may be configured for the socket unit. Use
this option to manage one or more symlinked alias names for a socket, binding their lifecycle together. Note
that if creation of a symlink fails this is not considered fatal for the socket unit, and the socket unit may
still start. If an empty string is assigned, the list of paths is reset. Defaults to an empty
list.</para></listitem>
</varlistentry>
<varlistentry>