Ohhh. THANKS a lot for explaining me that. :-) Sorry a silly job from my end .
I'll monitor logs for while and let you know about the progress. I had a quick question in previous reply. Could you please check that one ? Regards. Shahzaib On Thu, Mar 27, 2014 at 6:13 PM, Maxim Dounin <[email protected]> wrote: > Hello! > > On Thu, Mar 27, 2014 at 06:08:44PM +0500, shahzaib shahzaib wrote: > > > I upgraded nginx to nginx-1.4.7 and then issued the command nginx -s > > reload. Maybe nginx -s reload didn't actually used the latest binary. > Well, > > now i killed all other nginx using following command : > > > > killall -9 nginx > > nginx (to start new binary) > > The "nginx -s reload" is a configuration reload command. It won't > even try to change a binary, it will just sent a SIGHUP to a > running master process. > > See here for a documentation on how to control nginx properly: > http://nginx.org/en/docs/control.html > > -- > Maxim Dounin > http://nginx.org/ > > _______________________________________________ > nginx mailing list > [email protected] > http://mailman.nginx.org/mailman/listinfo/nginx >
_______________________________________________ nginx mailing list [email protected] http://mailman.nginx.org/mailman/listinfo/nginx
