Opened 10 years ago
Closed 10 years ago
#651 closed enhancement (wontfix)
Service 'stop' signal: replace TERM with QUIT
| Reported by: | https://stackoverflow.com/users/573152/bernard-rosset | Owned by: | |
|---|---|---|---|
| Priority: | minor | Milestone: | |
| Component: | nginx-package | Version: | 1.6.x |
| Keywords: | Cc: | ||
| uname -a: | |||
| nginx -V: |
nginx version: nginx/1.6.2
built by gcc 4.7.2 (Debian 4.7.2-5) |
||
Description
According to the nginx documentation about control/signals (http://nginx.org/en/docs/control.html), the TERM signal used in the packages (at least Debian's one) make nginx closing 'fast', instead of being 'graceful'.
To avoid prematurely closing connections to clients and to benefit from nginx 'graceful' shutdown, it would be nice if the default signal sent for shutdown was QUIT.
The current timers are OK, which would mean using: QUIT/30/KILL/5 with start-stop-daemon
Note:
See TracTickets
for help on using tickets.
If you are going to stop nginx, it usually means that you aren't doing anything "graceful". If you are to avoid closing connections with clients, you should use "reload" and "upgrade" commands instead. On the other hand, graceful stop as the default is likely to cause problems in many cases, as graceful termination may take a while.
It may be useful for some to add "gracefulstop" action like in the FreeBSD port instead. In my practice I've never used it though.