picnoir/Systemd
1
0
Fork 0
Code Issues Pull requests Projects Releases Wiki Activity

man: try to reword explanation of Sockets= a bit

Browse source
This commit is contained in:
Lennart Poettering 2014-10-20 21:06:14 +02:00
parent 659b937e67
commit 388ce34425
1 changed files with 16 additions and 13 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

29
man/systemd.service.xml
View file

@ -968,21 +968,24 @@
<term><varname>Sockets=</varname></term> <term><varname>Sockets=</varname></term>
<listitem><para>Specifies the name of <listitem><para>Specifies the name of
the socket units this service shall the socket units this service shall
inherit the sockets from when the inherit socket file descriptors
service is started. Normally it from when the service is
should not be necessary to use this started. Normally it should not be
setting as all sockets whose unit necessary to use this setting as all
socket file descriptors whose unit
shares the same name as the service shares the same name as the service
(ignoring the different suffix of course) (subject to the different unit name
are passed to the spawned suffix of course) are passed to the
process.</para> spawned process.</para>
<para>Note that the same socket may be <para>Note that the same socket file
passed to multiple processes at the descriptors may be passed to multiple
same time. Also note that a different processes simultaneously. Also note
service may be activated on incoming that a different service may be
traffic than that which inherits the activated on incoming socket traffic
sockets. Or in other words: the than the one which is ultimately
configured to inherit the socket file
descriptors. Or in other words: the
<varname>Service=</varname> setting of <varname>Service=</varname> setting of
<filename>.socket</filename> units <filename>.socket</filename> units
does not have to match the inverse of does not have to match the inverse of