mirror of
https://github.com/systemd/systemd.git
synced 2024-11-23 18:23:32 +08:00
man: wording and grammar updates
This includes regularly-submitted corrections to comma setting and orthographical mishaps that appeared in man/ in recent commits.
This commit is contained in:
parent
0b5a519c89
commit
d6ee7fa24f
@ -355,7 +355,7 @@
|
||||
syncing is unconditionally done
|
||||
immediately after a log message of
|
||||
priority CRIT, ALERT or EMERG has been
|
||||
logged, this setting hence applies
|
||||
logged. This setting hence applies
|
||||
only to messages of the levels ERR,
|
||||
WARNING, NOTICE, INFO, DEBUG. The
|
||||
default timeout is 5 minutes.
|
||||
|
@ -151,7 +151,7 @@ along with systemd; If not, see <http://www.gnu.org/licenses/>.
|
||||
<varlistentry>
|
||||
<term><option>--remain-after-exit</option></term>
|
||||
|
||||
<listitem><para>After the service's process terminated keep
|
||||
<listitem><para>After the service's process has terminated, keep
|
||||
the service around until it is explicitly stopped. This is
|
||||
useful to collect runtime information about the service after
|
||||
it finished running. Also see
|
||||
@ -164,10 +164,10 @@ along with systemd; If not, see <http://www.gnu.org/licenses/>.
|
||||
<varlistentry>
|
||||
<term><option>--send-sighup</option></term>
|
||||
|
||||
<listitem><para>When terminating the scope unit send a SIGHUP
|
||||
<listitem><para>When terminating the scope unit, send a SIGHUP
|
||||
immediately after SIGTERM. This is useful to indicate to
|
||||
shells and shell-like processes that the connection has been
|
||||
sewered. Also see <varname>SendSIGHUP=</varname> in
|
||||
severed. Also see <varname>SendSIGHUP=</varname> in
|
||||
<citerefentry><refentrytitle>systemd.kill</refentrytitle><manvolnum>5</manvolnum></citerefentry>.
|
||||
</para>
|
||||
</listitem>
|
||||
|
@ -123,8 +123,8 @@
|
||||
<constant>SIGHUP</constant> (if
|
||||
enabled with
|
||||
<varname>SendSIGHUP=</varname>). If
|
||||
then after a delay (configured via the
|
||||
<varname>TimeoutStopSec=</varname> option)
|
||||
then, after a delay (configured via the
|
||||
<varname>TimeoutStopSec=</varname> option),
|
||||
processes still remain, the
|
||||
termination request is repeated with
|
||||
the <constant>SIGKILL</constant>
|
||||
|
Loading…
Reference in New Issue
Block a user