On 11/29/2013 10:13 AM, Maxim Dounin wrote:
> Connections are handled by worker processes. On SIGHUP, master
> process parses new configuration and spawns new worker processes
> (while old workers still handle requests). Then it asks old
> workers to gracefully shutdown. That is, all the time
Hello!
On Fri, Nov 29, 2013 at 09:12:39AM -0200, Andre Nathan wrote:
> Hello
>
> In an apache webserver with many virtual hosts, a "reload" command can
> cause a (quick) unavailability of the service while apache re-reads its
> configuration files.
>
> Does anyone have any experience with this
Hello,
Sometimes reading the documentation might help :
http://nginx.org/en/docs/control.html
If you look at your service file, you'll notice that a 'reload' means
sending SIGHUP to the master process for the particular case of nginx.
I'll leave the conclusion to you, assuming that the doc is cle
Hello
In an apache webserver with many virtual hosts, a "reload" command can
cause a (quick) unavailability of the service while apache re-reads its
configuration files.
Does anyone have any experience with this on Nginx? Will sending it a
SIGHUP cause the main process to block and not be able to
