Welcome! Log In Create A New Profile

Advanced

Master process on reload

B.R.
June 29, 2016 01:06PM
Hello,

Kind of basic question about nginx behavior here.

On the docs page http://nginx.org/en/docs/control.html, 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.*
_______________________________________________
nginx mailing list
nginx@nginx.org
http://mailman.nginx.org/mailman/listinfo/nginx
Subject Author Posted

Master process on reload

B.R. June 29, 2016 01:06PM

Re: Master process on reload

Maxim Dounin June 29, 2016 01:40PM

Re: Master process on reload

B.R. June 29, 2016 03:36PM



Sorry, only registered users may post in this forum.

Click here to login

Online Users

Guests: 217
Record Number of Users: 8 on April 13, 2023
Record Number of Guests: 421 on December 02, 2018
Powered by nginx      Powered by FreeBSD      PHP Powered      Powered by MariaDB      ipv6 ready