Master process on reload

B.R. reallfqq-nginx at
Wed Jun 29 17:04:48 UTC 2016


Kind of basic question about nginx behavior here.

On the docs page, it is said :

> HUP -> changing configuration, keeping up with a changed time zone (only
> for FreeBSD and Linux), starting new worker processes with a new
> configuration, graceful shutdown of old worker processes

This is exact since the HUP signal is used to reload configuration and
spawn new workers with it.

However, a little bit further on the same page, in the on-the-fly upgrade
section, you got:

> Send the HUP signal to the old master process. The old master process will
> start new worker processes without re-reading the configuration. After
> that, all new processes can be shut down gracefully, by sending the QUIT
> signal to the new master process.

Is this behavior due to the USR2 signal previously sent, the old master
knowing it is the old one (and thus knowing it should avoid loading an
improper configuration suitable for another version)?
*B. R.*
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <>

More information about the nginx mailing list