shaba/systemd
1
0
Fork 0
mirror of https://github.com/systemd/systemd.git synced 2025-03-24 14:50:17 +03:00
Code

man: fix typo

Browse Source 
Follow-up for c896eb7ad65f4dbe968fdf01fa51e9ef4d2d11ed.
This commit is contained in:
Zbigniew Jędrzejewski-Szmek 2021-10-28 15:55:00 +02:00
parent 17cd1f627b
commit 77e289abb4
1 changed files with 5 additions and 5 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

10
man/sd_listen_fds.xml
View File

@ -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 <varname>Accept=yes</varname> 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 <citerefentry
changes and other changes made to the sockets will be visible to the service manager too. Most
importantly this means it's generally not a good idea to invoke <citerefentry
project='man-pages'><refentrytitle>shutdown</refentrytitle><manvolnum>2</manvolnum></citerefentry> 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.</para>
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.</para>
<para>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