shaba/systemd
1
0
Fork 0
mirror of https://github.com/systemd/systemd.git synced 2024-12-22 17:35:35 +03:00
Code

man: document socket requirement for systemd-socket-proxyd (#6535)

Browse Source 
Without this requirement, if proxy-to-nginx.socket was down, and the sysadmin
were to do:

    systemctl start proxy-to-nginx.service

then the service would come up without a configured socket, which doesn't make
sense.  Normally this isn't how we expect a socket-activated service to start,
but it's possible for an admin to do this (if the .socket were already running,
the systemd-socket-proxyd process will start effectively idle).  But the
.service shouldn't end up in a broken state if the .socket isn't already
listening.

Adding the explicit Requires: should ensure that an admin with this
configuration state can't accidentally break their system.
This commit is contained in:
dkg 2017-08-05 19:19:09 -04:00 committed by Zbigniew Jędrzejewski-Szmek
parent 8f968c7321
commit d7cefe8b2b
1 changed files with 4 additions and 0 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

4
man/systemd-socket-proxyd.xml
View File

@ -118,6 +118,8 @@ WantedBy=sockets.target]]></programlisting>
<programlisting><![CDATA[[Unit]
Requires=nginx.service
After=nginx.service
Requires=proxy-to-nginx.socket
After=proxy-to-nginx.service
[Service]
ExecStart=/usr/lib/systemd/systemd-socket-proxyd /tmp/nginx.sock
@ -159,6 +161,8 @@ WantedBy=sockets.target]]></programlisting>
<programlisting><![CDATA[[Unit]
Requires=nginx.service
After=nginx.service
Requires=proxy-to-nginx.service
After=proxy-to-nginx.service
JoinsNamespaceOf=nginx.service
[Service]