On Tue, Apr 21, 2009 at 01:11:45PM -0700, Payam Chychi wrote:

> Hey,
>
> I noticed that the graceful reload was not actually loading the new
> config changes and so ive had to use a hard down/start

I never saw this. Anyway, nginx should write the reason in error_log.

> kill -quit $master works
>
> i did also notice that nginx will not start with the following in the config:
> pid /var/log/nginx/nginx/pid;

Also, nginx should write the reason in error_log.

I use -QUIT only for in this sequence:

kill -USR2 `cat nginx.pid` # upgrade
kill -QUIT `cat nginx.pid.oldbin`

I use only -HUP to reload configuration

> so ive had to remove the line from the config...
> so it makes sense to why i cant stop it.. the pid is not able to write
> to a file
>
> -payam
>
>
> 2009/4/21 Igor Sysoev <is@rambler-co.ru>:
> > On Tue, Apr 21, 2009 at 09:50:09AM -0700, Payam Chychi wrote:
> >
> >> hey Guys,
> >>
> >> Anyone else notice that in the resent *.52 release stopping/starting
> >> nginx does not restart the process? I manually have to kill -9 the
> >> master and each child...
> >
> > BTW, why do you use stop/start instead of graceful reload ?
> >
> >
> > --
> > Igor Sysoev
> > http://sysoev.ru/en/
> >
> >
>
>
>
> --
> Payam Tarverdyan Chychi
> Network Security Specialist / Network Engineer

--
Igor Sysoev
http://sysoev.ru/en/