2012-07-20 01:47:10 +04:00
<?xml version='1.0'?> <!-- * - nxml - * -->
<?xml-stylesheet type="text/xsl" href="http://docbook.sourceforge.net/release/xsl/current/xhtml/docbook.xsl"?>
< !DOCTYPE refentry PUBLIC "-//OASIS//DTD DocBook XML V4.2//EN"
"http://www.oasis-open.org/docbook/xml/4.2/docbookx.dtd">
<!--
This file is part of systemd.
Copyright 2012 Lennart Poettering
systemd is free software; you can redistribute it and/or modify it
under the terms of the GNU Lesser General Public License as published by
the Free Software Foundation; either version 2.1 of the License, or
(at your option) any later version.
systemd is distributed in the hope that it will be useful, but
WITHOUT ANY WARRANTY; without even the implied warranty of
MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the GNU
Lesser General Public License for more details.
You should have received a copy of the GNU Lesser General Public License
along with systemd; If not, see <http: / / w w w . g n u . o r g / l i c e n s e s /> .
-->
<refentry id= "systemd.kill" >
<refentryinfo >
<title > systemd.kill</title>
<productname > systemd</productname>
<authorgroup >
<author >
<contrib > Developer</contrib>
<firstname > Lennart</firstname>
<surname > Poettering</surname>
<email > lennart@poettering.net</email>
</author>
</authorgroup>
</refentryinfo>
<refmeta >
<refentrytitle > systemd.kill</refentrytitle>
<manvolnum > 5</manvolnum>
</refmeta>
<refnamediv >
<refname > systemd.kill</refname>
<refpurpose > Kill environment configuration</refpurpose>
</refnamediv>
<refsynopsisdiv >
2013-02-14 07:46:37 +04:00
<para > <filename > <replaceable > service</replaceable> .service</filename> ,
<filename > <replaceable > socket</replaceable> .socket</filename> ,
<filename > <replaceable > mount</replaceable> .mount</filename> ,
<filename > <replaceable > swap</replaceable> .swap</filename> </para>
2012-07-20 01:47:10 +04:00
</refsynopsisdiv>
<refsect1 >
<title > Description</title>
<para > Unit configuration files for services, sockets,
mount points and swap devices share a subset of
configuration options which define the process killing
parameters of spawned processes.</para>
<para > This man page lists the configuration options
shared by these four unit types. See
<citerefentry > <refentrytitle > systemd.unit</refentrytitle> <manvolnum > 5</manvolnum> </citerefentry>
for the common options of all unit configuration
files, and
<citerefentry > <refentrytitle > systemd.service</refentrytitle> <manvolnum > 5</manvolnum> </citerefentry> ,
<citerefentry > <refentrytitle > systemd.socket</refentrytitle> <manvolnum > 5</manvolnum> </citerefentry> ,
<citerefentry > <refentrytitle > systemd.swap</refentrytitle> <manvolnum > 5</manvolnum> </citerefentry>
and
<citerefentry > <refentrytitle > systemd.mount</refentrytitle> <manvolnum > 5</manvolnum> </citerefentry>
for more information on the specific unit
configuration files. The execution specific
configuration options are configured in the [Service],
Reword sentences that contain psuedo-English "resp."
As you likely know, Arch Linux is in the process of moving to systemd.
So I was reading through the various systemd docs and quickly became
baffled by this new abbreviation "resp.", which I've never seen before
in my English-mother-tongue life.
Some quick Googling turned up a reference:
<http://www.transblawg.eu/index.php?/archives/870-Resp.-and-other-non-existent-English-wordsNicht-existente-englische-Woerter.html>
I guess it's a literal translation of the German "Beziehungsweise", but
English doesn't work the same way. The word "respectively" is used
exclusively to provide an ordering connection between two lists. E.g.
"the prefixes k, M, and G refer to kilo-, mega-, and giga-,
respectively." It is also never abbreviated to "resp." So the sentence
"Sets the default output resp. error output for all services and
sockets" makes no sense to a natural English speaker.
This patch removes all instances of "resp." in the man pages and
replaces them with sentences which are much more clear and, hopefully,
grammatically valid. In almost all instances, it was simply replacing
"resp." with "or," which the original author (Lennart?) could probably
just do in the future.
The only other instances of "resp." are in the src/ subtree, which I
don't feel privileged to correct.
Signed-off-by: Andrew Eikum <aeikum@codeweavers.com>
2012-10-15 22:59:12 +04:00
[Socket], [Mount], or [Swap] section, depending on the unit
2012-07-20 01:47:10 +04:00
type.</para>
</refsect1>
<refsect1 >
<title > Options</title>
2013-01-26 19:47:16 +04:00
<variablelist class= 'unit-directives' >
2012-07-20 01:47:10 +04:00
<varlistentry >
<term > <varname > KillMode=</varname> </term>
<listitem > <para > Specifies how
processes of this service shall be
killed. One of
<option > control-group</option> ,
<option > process</option> ,
<option > none</option> .</para>
<para > If set to
2013-09-12 23:12:49 +04:00
<option > control-group</option> , all
2012-07-20 01:47:10 +04:00
remaining processes in the control
group of this unit will be terminated
on unit stop (for services: after the
stop command is executed, as
configured with
<varname > ExecStop=</varname> ). If set
2013-09-12 23:12:49 +04:00
to <option > process</option> , only the
2012-07-20 01:47:10 +04:00
main process itself is killed. If set
2013-09-12 23:12:49 +04:00
to <option > none</option> , no process is
2012-07-20 01:47:10 +04:00
killed. In this case only the stop
command will be executed on unit
stop, but no process be killed
otherwise. Processes remaining alive
after stop are left in their control
group and the control group continues
to exist after stop unless it is
empty. Defaults to
<option > control-group</option> .</para>
<para > Processes will first be
2013-07-30 03:54:59 +04:00
terminated via
<constant > SIGTERM</constant> (unless
the signal to send is changed via
<varname > KillSignal=</varname> ). Optionally,
this is immediately followed by a
<constant > SIGHUP</constant> (if
enabled with
<varname > SendSIGHUP=</varname> ). If
2013-08-05 03:13:28 +04:00
then, after a delay (configured via the
<varname > TimeoutStopSec=</varname> option),
2012-07-20 01:47:10 +04:00
processes still remain, the
termination request is repeated with
2013-07-30 03:54:59 +04:00
the <constant > SIGKILL</constant>
signal (unless this is disabled via
the <varname > SendSIGKILL=</varname>
2012-07-20 01:47:10 +04:00
option). See
<citerefentry > <refentrytitle > kill</refentrytitle> <manvolnum > 2</manvolnum> </citerefentry>
for more
information.</para> </listitem>
</varlistentry>
<varlistentry >
<term > <varname > KillSignal=</varname> </term>
<listitem > <para > Specifies which signal
to use when killing a
2013-06-29 20:09:14 +04:00
service. Defaults to <constant > SIGTERM</constant> .
2012-07-20 01:47:10 +04:00
</para> </listitem>
</varlistentry>
2013-07-30 03:54:59 +04:00
<varlistentry >
<term > <varname > SendSIGHUP=</varname> </term>
<listitem > <para > Specifies whether to
send <constant > SIGHUP</constant> to
remaining processes immediately after
sending the signal configured with
<varname > KillSignal=</varname> . This
is useful to indicate to shells and
shell-like programs that their
connection has been severed. Takes a
boolean value. Defaults to "no".
</para> </listitem>
</varlistentry>
2012-07-20 01:47:10 +04:00
<varlistentry >
<term > <varname > SendSIGKILL=</varname> </term>
<listitem > <para > Specifies whether to
2013-06-29 20:09:14 +04:00
send <constant > SIGKILL</constant> to remaining processes
2012-07-20 01:47:10 +04:00
after a timeout, if the normal
shutdown procedure left processes of
the service around. Takes a boolean
value. Defaults to "yes".
</para> </listitem>
</varlistentry>
2013-07-30 03:54:59 +04:00
2012-07-20 01:47:10 +04:00
</variablelist>
</refsect1>
<refsect1 >
<title > See Also</title>
<para >
<citerefentry > <refentrytitle > systemd</refentrytitle> <manvolnum > 1</manvolnum> </citerefentry> ,
<citerefentry > <refentrytitle > systemctl</refentrytitle> <manvolnum > 8</manvolnum> </citerefentry> ,
<citerefentry > <refentrytitle > journalctl</refentrytitle> <manvolnum > 8</manvolnum> </citerefentry> ,
<citerefentry > <refentrytitle > systemd.unit</refentrytitle> <manvolnum > 5</manvolnum> </citerefentry> ,
<citerefentry > <refentrytitle > systemd.service</refentrytitle> <manvolnum > 5</manvolnum> </citerefentry> ,
<citerefentry > <refentrytitle > systemd.socket</refentrytitle> <manvolnum > 5</manvolnum> </citerefentry> ,
<citerefentry > <refentrytitle > systemd.swap</refentrytitle> <manvolnum > 5</manvolnum> </citerefentry> ,
<citerefentry > <refentrytitle > systemd.mount</refentrytitle> <manvolnum > 5</manvolnum> </citerefentry> ,
2013-01-15 07:08:33 +04:00
<citerefentry > <refentrytitle > systemd.exec</refentrytitle> <manvolnum > 5</manvolnum> </citerefentry> ,
<citerefentry > <refentrytitle > systemd.directives</refentrytitle> <manvolnum > 7</manvolnum> </citerefentry>
2012-07-20 01:47:10 +04:00
</para>
</refsect1>
</refentry>