Files
systemd/man
dkg d7cefe8b2b man: document socket requirement for systemd-socket-proxyd (#6535)
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.
2017-08-05 19:19:09 -04:00
..
2017-02-21 16:28:04 +01:00
2017-02-21 16:28:04 +01:00
2017-08-03 17:36:21 -04:00
2017-02-21 16:28:04 +01:00
2017-02-21 16:28:04 +01:00
2017-07-03 10:33:42 -04:00
2016-07-04 17:10:23 +02:00
2017-05-31 19:24:47 -04:00
2017-01-19 16:54:22 +01:00
2017-02-21 16:28:04 +01:00
2016-10-12 23:02:44 +02:00
2017-02-21 16:28:04 +01:00
2017-08-03 17:36:21 -04:00
2017-01-19 16:54:22 +01:00
2017-02-21 16:28:04 +01:00
2017-08-03 17:36:21 -04:00
2017-08-03 17:36:21 -04:00
2017-02-21 16:28:04 +01:00
2017-02-21 16:28:04 +01:00
2017-02-21 16:28:04 +01:00
2016-11-08 10:51:35 +01:00