nginx custom script location
jamie at tomoyolinux.co.uk
Wed May 16 20:52:27 UTC 2012
On 16 May 2012 20:09, Tomasz Torcz <tomek at pipebreaker.pl> wrote:
> On Wed, May 16, 2012 at 06:10:08PM +0100, Jamie Nguyen wrote:
>> On 16 May 2012 08:16, Tomasz Torcz <tomek at pipebreaker.pl> wrote:
>> > Also, implementing socket-activation in nginx would make it upgradable
>> > without losing any connections.
>> Sorry, could you clarify? I don't see how that would help in this situation.
>> AFAIK, systemd socket activation is useful either for parallelization
>> during system startup, or on-demand activation. The former doesn't
>> help, and the latter is definitely not what we want for a web server.
> If the new request comes during nginx restart¹, it won't be lost.
> Socket is always opened by systemd and the connection will be buffered
> until new nginx is ready to server it.
> ¹ in time between old nginx closing its socket and new nginx creating new
Will look into this. Thanks for clarifying!
More information about the devel