On Mon, Apr 10, 2017 at 1:04 PM, B.R. via nginx wrote:
> You could have got your answer yourself by Reading The... Fine? Manual:
> https://nginx.org/en/docs/control.html
>
> There are tons of interesting pieces of informations there, by the nature
> of said docs...
> I suggest you take a look at
I do not know anything about third-party modules. I'll let experts on the
lua one answering that one.
The baseline is: you should not need to.
---
*B. R.*
On Mon, Apr 10, 2017 at 11:31 PM, Alex Samad wrote:
> But long live sessions are closed and I've had lua session information
> persist with a
But long live sessions are closed and I've had lua session information
persist with a reload. Needed a restart
A
On Sun, 9 Apr 2017 at 21:35, B.R. via nginx wrote:
> You could have got your answer yourself by Reading The... Fine? Manual:
> https://nginx.org/en/docs/control.html
>
> There are ton
You could have got your answer yourself by Reading The... Fine? Manual:
https://nginx.org/en/docs/control.html
There are tons of interesting pieces of informations there, by the nature
of said docs...
I suggest you take a look at everything: https://nginx.org/en/docs/
---
*B. R.*
On Sun, Apr 9,
Thanks a ton Lucas.
Just checked reloading, and the previous proxy-session was intact !!
Thanks a ton again.
And sorry I missed your name in the credits, you too had helped a greate
deal yesterday, and today too !!
Thanks a ton again !!!
Thanks and Regards,
Ajay
On Sun, Apr 9, 2017 at 7:29 PM,
Hi Ajay,
If you generate the configuration, and issue a nginx reload – it won't cause
any downtime. The master process will reread the configuration, start new
workers, and gracefully shut down the old ones.
There's absolutely no downtime involved in this process.
From: nginx mailto:nginx-boun