summaryrefslogtreecommitdiff
path: root/man/systemd.service.xml
diff options
context:
space:
mode:
authorJason St. John <jstjohn@purdue.edu>2014-02-14 22:07:22 -0500
committerZbigniew Jędrzejewski-Szmek <zbyszek@in.waw.pl>2014-02-14 22:08:10 -0500
commitb200a92cdc47b204e2ed7fbdd1eaf15abfd019c6 (patch)
tree72268b1503702cac96b7ac55591879dbc17856ec /man/systemd.service.xml
parent6db2742802b70938f0f2d373110ed734d4fb9813 (diff)
man: use spaces instead of tabs
Several sections of the man pages included intermixed tabs and spaces; this commit replaces all tabs with spaces.
Diffstat (limited to 'man/systemd.service.xml')
-rw-r--r--man/systemd.service.xml46
1 files changed, 23 insertions, 23 deletions
diff --git a/man/systemd.service.xml b/man/systemd.service.xml
index 454cde4b49..8ad665643d 100644
--- a/man/systemd.service.xml
+++ b/man/systemd.service.xml
@@ -751,29 +751,29 @@ ExecStart=/bin/echo $ONE $TWO ${TWO}</programlisting>
be considered if the service does not implement
a signal handler and exits as a direct result
of receiving the signal. For example:
- <programlisting>SuccessExitStatus=1 2 8 <constant>SIGKILL</constant></programlisting>
- ensures that exit codes 1, 2, 8 and
- the termination signal
- <constant>SIGKILL</constant> are
- considered clean service terminations.
- </para>
-
- <para>Note that if a process has a
- signal handler installed and exits by
- calling
- <citerefentry><refentrytitle>_exit</refentrytitle><manvolnum>2</manvolnum></citerefentry>
- in response to a signal, the
- information about the signal is lost.
- Programs should instead perform cleanup and kill themselves with the same signal instead. See
- <ulink url="http://www.cons.org/cracauer/sigint.html">Proper handling of SIGINT/SIGQUIT — How to be a proper program</ulink>.</para>
-
- <para>This option may appear more than once
- in which case the list of successful
- exit statuses is merged. If the empty
- string is assigned to this option, the
- list is reset, all prior assignments
- of this option will have no
- effect.</para></listitem>
+ <programlisting>SuccessExitStatus=1 2 8 <constant>SIGKILL</constant></programlisting>
+ ensures that exit codes 1, 2, 8 and
+ the termination signal
+ <constant>SIGKILL</constant> are
+ considered clean service terminations.
+ </para>
+
+ <para>Note that if a process has a
+ signal handler installed and exits by
+ calling
+ <citerefentry><refentrytitle>_exit</refentrytitle><manvolnum>2</manvolnum></citerefentry>
+ in response to a signal, the
+ information about the signal is lost.
+ Programs should instead perform cleanup and kill themselves with the same signal instead. See
+ <ulink url="http://www.cons.org/cracauer/sigint.html">Proper handling of SIGINT/SIGQUIT — How to be a proper program</ulink>.</para>
+
+ <para>This option may appear more than once
+ in which case the list of successful
+ exit statuses is merged. If the empty
+ string is assigned to this option, the
+ list is reset, all prior assignments
+ of this option will have no
+ effect.</para></listitem>
</varlistentry>
<varlistentry>