From 77e289abb4f573f9863bbc0d37d76c8ad031aef0 Mon Sep 17 00:00:00 2001 From: =?UTF-8?q?Zbigniew=20J=C4=99drzejewski-Szmek?= Date: Thu, 28 Oct 2021 15:55:00 +0200 Subject: [PATCH] man: fix typo Follow-up for c896eb7ad65f4dbe968fdf01fa51e9ef4d2d11ed. --- man/sd_listen_fds.xml | 10 +++++----- 1 file changed, 5 insertions(+), 5 deletions(-) diff --git a/man/sd_listen_fds.xml b/man/sd_listen_fds.xml index 83d94c7903..9e0be7fbf7 100644 --- a/man/sd_listen_fds.xml +++ b/man/sd_listen_fds.xml @@ -56,13 +56,13 @@ (in which case the kernel closes them automatically). Note that the file descriptors received by daemons are duplicates of the file descriptors the service manager originally allocated and bound and of which it continuously keeps a copy (except if Accept=yes is used). This means any socket option - changes and other changes made to the sockets will visible to the service manager too. Most importanly - this means it's generally not a good idea to invoke shutdown2 on such sockets, since it will shut down communication on the file descriptor the service manager holds for - the same socket, too. Also note that if a daemon is restarted (and its associated sockets are not) it - will receive file descriptors to the very same sockets as the earlier invocations, thus all socket - options applied then will still apply. + the same socket too. Also note that if a daemon is restarted (and its associated sockets are not) it will + receive file descriptors to the very same sockets as the earlier invocations, thus all socket options + applied then will still apply. If a daemon receives more than one file descriptor, they will be passed in the same order as configured in the systemd socket unit file (see