From 3c86d34cf1e381ade10dcc41c655c98b2d489c8d Mon Sep 17 00:00:00 2001 From: Lennart Poettering Date: Thu, 20 Jun 2013 23:25:23 +0200 Subject: [PATCH 1/1] man: document that shutdown() is only sometimes OK on sockets passed in via socket activation --- man/systemd.socket.xml | 27 +++++++++++++++++---------- 1 file changed, 17 insertions(+), 10 deletions(-) diff --git a/man/systemd.socket.xml b/man/systemd.socket.xml index f1e7d408a..040305c63 100644 --- a/man/systemd.socket.xml +++ b/man/systemd.socket.xml @@ -374,23 +374,30 @@ and only one service unit is spawned for all connections (also see above). This value is ignored for - datagram sockets and FIFOs where - a single service unit unconditionally + datagram sockets and FIFOs where a + single service unit unconditionally handles all incoming traffic. Defaults to . For performance reasons, it is recommended to write new daemons only in a way that is suitable for - . A daemon - listening on an AF_UNIX socket may, but does not need to, call + . A + daemon listening on an AF_UNIX socket + may, but does not need to, call close2 - or + on the received socket before + exiting. However, it must not unlink + the socket from a filesystem. It + should note invoke shutdown2 - on the received socket before exiting. However, - it must not unlink the socket from a - filesystem. This option is mostly useful - to allow daemons designed for usage with - inetd8, + on sockets it got with + Accept=false, but + it may do so for sockets it got with + Accept=true set. + Setting Accept=true + is mostly useful to allow daemons + designed for usage with + inetd8 to work unmodified with systemd socket activation. -- 2.30.2