summaryrefslogtreecommitdiff
path: root/man/systemd.service.xml
diff options
context:
space:
mode:
authorJan Engelhardt <jengelh@inai.de>2013-09-12 21:12:49 +0200
committerLennart Poettering <lennart@poettering.net>2013-09-12 22:09:57 +0200
commit79640424059328268b9fb6c5fa8eb777b27a177e (patch)
treee3579216d1afd438e667044869dcdf9c732ef18c /man/systemd.service.xml
parent982e44dbc3e70c97e83464a30354b80973d52b41 (diff)
man: wording and grammar updates
This is a recurring submission and includes corrections to various issue spotted. I guess I can just skip over reporting ubiquitous comma placement fixes… Highligts in this particular commit: - the "unsigned" type qualifier is completed to form a full type "unsigned int" - alphabetic -> lexicographic (that way we automatically define how numbers get sorted)
Diffstat (limited to 'man/systemd.service.xml')
-rw-r--r--man/systemd.service.xml62
1 files changed, 31 insertions, 31 deletions
diff --git a/man/systemd.service.xml b/man/systemd.service.xml
index 1eb5f39628..8eda85f62d 100644
--- a/man/systemd.service.xml
+++ b/man/systemd.service.xml
@@ -140,13 +140,13 @@
<para>If set to
<option>simple</option> (the default
value if <varname>BusName=</varname>
- is not specified) it is expected that
+ is not specified), it is expected that
the process configured with
<varname>ExecStart=</varname> is the
main process of the service. In this
mode, if the process offers
functionality to other processes on
- the system its communication channels
+ the system, its communication channels
should be installed before the daemon
is started up (e.g. sockets set up by
systemd, via socket activation), as
@@ -154,14 +154,14 @@
starting follow-up units.</para>
<para>If set to
- <option>forking</option> it is
+ <option>forking</option>, it is
expected that the process configured
with <varname>ExecStart=</varname>
will call <function>fork()</function>
as part of its start-up. The parent process is
expected to exit when start-up is
complete and all communication
- channels set up. The child continues
+ channels are set up. The child continues
to run as the main daemon
process. This is the behavior of
traditional UNIX daemons. If this
@@ -210,7 +210,7 @@
starting up. systemd will proceed
starting follow-up units after this
notification message has been sent. If
- this option is used
+ this option is used,
<varname>NotifyAccess=</varname> (see
below) should be set to open access to
the notification socket provided by
@@ -220,7 +220,7 @@
<option>main</option>. Note that
currently
<varname>Type=</varname><option>notify</option>
- won't work if used in combination with
+ will not work if used in combination with
<varname>PrivateNetwork=</varname><option>yes</option>.</para>
<para>Behavior of
@@ -262,7 +262,7 @@
guessing algorithm might come to
incorrect conclusions if a daemon
consists of more than one process. If
- the main PID cannot be determined
+ the main PID cannot be determined,
failure detection and automatic
restarting of a service will not work
reliably. Defaults to
@@ -327,7 +327,7 @@
<filename>.desktop</filename> files.
Lone semicolons may be escaped as
<literal>\;</literal>. If the empty
- string is assigned to this option the
+ string is assigned to this option, the
list of commands to start is reset,
prior assignments of this option will
have no effect.</para>
@@ -383,19 +383,19 @@
executed process, followed by the
further arguments specified. If the
absolute filename is prefixed with
- <literal>-</literal> an exit code of
+ <literal>-</literal>, an exit code of
the command normally considered a
failure (i.e. non-zero exit status or
abnormal exit due to signal) is ignored
and considered success. If both
<literal>-</literal> and
- <literal>@</literal> are used they
+ <literal>@</literal> are used, they
can appear in either order.</para>
<para>Note that this setting does not
directly support shell command
lines. If shell command lines are to
- be used they need to be passed
+ be used, they need to be passed
explicitly to a shell implementation
of some kind. Example:</para>
<programlisting>ExecStart=/bin/sh -c 'dmesg | tac'
@@ -471,7 +471,7 @@
<varname>KillMode=</varname> setting
(see
<citerefentry><refentrytitle>systemd.kill</refentrytitle><manvolnum>5</manvolnum></citerefentry>). If
- this option is not specified the
+ this option is not specified, the
process is terminated right-away when
service stop is requested. Specifier
and environment variable substitution
@@ -567,11 +567,11 @@
regularly with "WATCHDOG=1" (i.e. the
"keep-alive ping"). If the time
between two such calls is larger than
- the configured time then the service
+ the configured time, then the service
is placed in a failure state. By
setting <varname>Restart=</varname> to
<option>on-failure</option> or
- <option>always</option> the service
+ <option>always</option>, the service
will be automatically restarted. The
time configured here will be passed to
the executed service process in the
@@ -580,7 +580,7 @@
daemons to automatically enable the
keep-alive pinging logic if watchdog
support is enabled for the service. If
- this option is used
+ this option is used,
<varname>NotifyAccess=</varname> (see
below) should be set to open access to
the notification socket provided by
@@ -621,9 +621,9 @@
<option>on-watchdog</option>,
<option>on-abort</option>, or
<option>always</option>. If set to
- <option>no</option> (the default) the
+ <option>no</option> (the default), the
service will not be restarted. If set to
- <option>on-success</option> it will be
+ <option>on-success</option>, it will be
restarted only when the service process
exits cleanly.
In this context, a clean exit means
@@ -631,7 +631,7 @@
<constant>SIGHUP</constant>, <constant>SIGINT</constant>, <constant>SIGTERM</constant>, or <constant>SIGPIPE</constant>, and
additionally, exit statuses and signals
specified in <varname>SuccessExitStatus=</varname>.
- If set to <option>on-failure</option>
+ If set to <option>on-failure</option>,
the service will be restarted when the
process exits with an nonzero exit code,
is terminated by a signal (including on
@@ -639,17 +639,17 @@
service reload) times out, and when the
configured watchdog timeout is triggered.
If set to
- <option>on-abort</option> the service
+ <option>on-abort</option>, the service
will be restarted only if the service
process exits due to an uncaught
signal not specified as a clean exit
status.
If set to
- <option>on-watchdog</option> the service
+ <option>on-watchdog</option>, the service
will be restarted only if the watchdog
timeout for the service expires.
If set to
- <option>always</option> the service
+ <option>always</option>, the service
will be restarted regardless whether
it exited cleanly or not, got
terminated abnormally by a signal or
@@ -682,7 +682,7 @@
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
+ assigned to this option, the list is
reset, all prior assignments of this
option will have no
effect.</para></listitem>
@@ -712,7 +712,7 @@
option may appear more than once in
which case the list of restart preventing
statuses is merged. If the empty
- string is assigned to this option the
+ string is assigned to this option, the
list is reset, all prior assignments
of this option will have no
effect.</para></listitem>
@@ -790,13 +790,13 @@
<option>none</option> (the default),
<option>main</option> or
<option>all</option>. If
- <option>none</option> no daemon status
+ <option>none</option>, no daemon status
updates are accepted from the service
processes, all status update messages
- are ignored. If <option>main</option>
+ are ignored. If <option>main</option>,
only service updates sent from the
main process of the service are
- accepted. If <option>all</option> all
+ accepted. If <option>all</option>, all
services updates from all members of
the service's control group are
accepted. This option should be set to
@@ -805,8 +805,8 @@
<varname>Type=notify</varname> or
<varname>WatchdogSec=</varname> (see
above). If those options are used but
- <varname>NotifyAccess=</varname> not
- configured it will be implicitly set
+ <varname>NotifyAccess=</varname> is not
+ configured, it will be implicitly set
to
<option>main</option>.</para></listitem>
</varlistentry>
@@ -841,7 +841,7 @@
<para>This option may appear more than
once, in which case the list of socket
units is merged. If the empty string
- is assigned to this option the list of
+ is assigned to this option, the list of
sockets is reset, all prior uses of
this setting will have no
effect.</para></listitem>
@@ -852,12 +852,12 @@
<term><varname>StartLimitBurst=</varname></term>
<listitem><para>Configure service
- start rate limiting. By default
+ start rate limiting. By default,
services which are started more often
than 5 times within 10s are not
permitted to start any more times
until the 10s interval ends. With
- these two options this rate limiting
+ these two options, this rate limiting
may be modified. Use
<varname>StartLimitInterval=</varname>
to configure the checking interval