Your message dated Wed, 9 Nov 2016 11:47:32 -0600
with message-id <[email protected]>
and subject line
has caused the Debian Bug report #821114,
regarding nginx: Please use KillSignal=SIGQUIT in systemd service
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact [email protected]
immediately.)
--
821114: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=821114
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
Package: nginx
Version: 1.6.2-3
Severity: normal
User: [email protected]
Hi,
Wouldn't it be better to use KillSignal=SIGQUIT in the .service file
rather than using this hack?
ExecStop=-/sbin/start-stop-daemon --quiet --stop --retry QUIT/5 --pidfile
/run/nginx.pid
Is it necessary really necessary to send QUIT, then TERM and then KILL?
Cheers,
Laurent Bigonville
-- System Information:
Debian Release: stretch/sid
APT prefers unstable-debug
APT policy: (500, 'unstable-debug'), (500, 'unstable'), (1,
'experimental-debug'), (1, 'experimental')
Architecture: amd64 (x86_64)
Foreign Architectures: i386
Kernel: Linux 4.5.0-trunk-amd64 (SMP w/4 CPU cores)
Locale: LANG=fr_BE.UTF-8, LC_CTYPE=fr_BE.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)
--- End Message ---
--- Begin Message ---
Control: tags 821114 + wontfix
--- End Message ---
