summaryrefslogtreecommitdiff
path: root/man/systemd.exec.xml
diff options
context:
space:
mode:
authorZbigniew Jędrzejewski-Szmek <zbyszek@in.waw.pl>2022-03-09 14:45:59 +0100
committerLennart Poettering <lennart@poettering.net>2022-03-18 10:22:20 +0100
commitf60b0813ea14d795788208fdb5cac076f5539470 (patch)
treef38c52de7ec61783c16254b5c789da0410791bd7 /man/systemd.exec.xml
parent4f5c24857b8206a53f05e151e690ff599c481b16 (diff)
downloadsystemd-f60b0813ea14d795788208fdb5cac076f5539470.tar.gz
man/systemd.exec: tweak markup a bit
Diffstat (limited to 'man/systemd.exec.xml')
-rw-r--r--man/systemd.exec.xml21
1 files changed, 11 insertions, 10 deletions
diff --git a/man/systemd.exec.xml b/man/systemd.exec.xml
index 6f1fa6338a..89a6c33759 100644
--- a/man/systemd.exec.xml
+++ b/man/systemd.exec.xml
@@ -2718,8 +2718,8 @@ SystemCallErrorNumber=EPERM</programlisting>
<varname>StandardInput=</varname>, see above. If <replaceable>path</replaceable> refers to a regular file
on the filesystem, it is opened (created if it doesn't exist yet) for writing at the beginning of the file,
but without truncating it.
- If standard input and output are directed to the same file path, it is opened only once, for reading as well
- as writing and duplicated. This is particularly useful when the specified path refers to an
+ If standard input and output are directed to the same file path, it is opened only once — for reading as well
+ as writing — and duplicated. This is particularly useful when the specified path refers to an
<constant>AF_UNIX</constant> socket in the file system, as in that case only a
single stream connection is created for both input and output.</para>
@@ -2745,16 +2745,17 @@ SystemCallErrorNumber=EPERM</programlisting>
<para><option>socket</option> connects standard output to a socket acquired via socket activation. The
semantics are similar to the same option of <varname>StandardInput=</varname>, see above.</para>
- <para>The <option>fd:<replaceable>name</replaceable></option> option connects standard output to a specific,
- named file descriptor provided by a socket unit. A name may be specified as part of this option, following a
- <literal>:</literal> character (e.g. <literal>fd:foobar</literal>). If no name is specified, the name
+ <para>The <option>fd:<replaceable>name</replaceable></option> option connects standard output to a
+ specific, named file descriptor provided by a socket unit. A name may be specified as part of this
+ option, following a <literal>:</literal> character
+ (e.g. <literal>fd:<replaceable>foobar</replaceable></literal>). If no name is specified, the name
<literal>stdout</literal> is implied (i.e. <literal>fd</literal> is equivalent to
- <literal>fd:stdout</literal>). At least one socket unit defining the specified name must be provided via the
- <varname>Sockets=</varname> option, and the file descriptor name may differ from the name of its containing
- socket unit. If multiple matches are found, the first one will be used. See
+ <literal>fd:stdout</literal>). At least one socket unit defining the specified name must be provided
+ via the <varname>Sockets=</varname> option, and the file descriptor name may differ from the name of
+ its containing socket unit. If multiple matches are found, the first one will be used. See
<varname>FileDescriptorName=</varname> in
- <citerefentry><refentrytitle>systemd.socket</refentrytitle><manvolnum>5</manvolnum></citerefentry> for more
- details about named descriptors and their ordering.</para>
+ <citerefentry><refentrytitle>systemd.socket</refentrytitle><manvolnum>5</manvolnum></citerefentry>
+ for more details about named descriptors and their ordering.</para>
<para>If the standard output (or error output, see below) of a unit is connected to the journal or
the kernel log buffer, the unit will implicitly gain a dependency of type <varname>After=</varname>