If we turn this off, is it possible for systemd to send nginx the reload signal
as opposed to a complete restart?
Of course. If you look the attached service file, you can notice that
the reload is fully operational. Here is a proof.
# Ensure that nginx is stopped first
root@complexe:~#
On Sun, Oct 27, 2013 at 05:32:48PM +0100, Adrien CLERC wrote:
Package: nginx
Version: 1.4.3-2
Severity: minor
--- Please enter the report below this line. ---
Hi,
In the systemd service file, the two following directive are used:
Type=forking
PIDFile=/run/nginx.pid
However, when running
Package: nginx
Version: 1.4.3-2
Severity: minor
--- Please enter the report below this line. ---
Hi,
In the systemd service file, the two following directive are used:
Type=forking
PIDFile=/run/nginx.pid
However, when running systemd, it's easier to let systemd handle the PID
stuff, and tell
Using 'daemon off;' in nginx will likely cause issues when a user wants to run
'nginx -s reload'. The reload signal allows nginx to not drop any connections
while bringing up a new config. This is one of the reasons that using
supervisord is disliked so much.
This is done by opening a new master
4 matches
Mail list logo
