summaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authorLennart Poettering <lennart@poettering.net>2010-10-05 20:51:00 +0200
committerLennart Poettering <lennart@poettering.net>2010-10-05 20:51:00 +0200
commitf72192c0c91b3adc92dc34b9ebead51dd215d2b2 (patch)
treea2cee4a510f8dbd4e0a41e365841ba8469a11ec3
parente62e6670f77a886d26fbfe612e6f4fa0c2e0c98b (diff)
man: document Sockets= switch
-rw-r--r--man/systemd.service.xml27
1 files changed, 27 insertions, 0 deletions
diff --git a/man/systemd.service.xml b/man/systemd.service.xml
index d573ec6f96..8f455ea4c7 100644
--- a/man/systemd.service.xml
+++ b/man/systemd.service.xml
@@ -602,6 +602,33 @@
<varname>Type=notify</varname> (see above).</para></listitem>
</varlistentry>
+ <varlistentry>
+ <term><varname>Sockets=</varname></term>
+ <listitem><para>Specifies the name of
+ the socket units this service shall
+ inherit the sockets from when the
+ service (ignoring the different suffix
+ of course) is started. Normally it
+ should not be necessary to use this
+ setting as all sockets whose unit
+ shares the same name as the service
+ are passed to the spawned
+ process.</para>
+
+ <para>Note that the same socket may be
+ passed to multiple processes at the
+ same time. Also note that a different
+ service may be activated on incoming
+ traffic than inherits the sockets. Or
+ in other words: The
+ <varname>Service=</varname> setting of
+ <filename>.socket</filename> units
+ doesn't have to match the inverse of the
+ <varname>Sockets=</varname> setiing of
+ the <filename>.service</filename> it
+ refers to.</para></listitem>
+ </varlistentry>
+
</variablelist>
</refsect1>