checking config outputs a pid file

Cherife Li cherife at
Tue May 27 09:48:57 MSD 2008

On 05/27/08 12:52, Jeffrey 'jf' Lim wrote:
> On Tue, May 27, 2008 at 11:53 AM, Cherife Li <cherife at 
> <mailto:cherife at>> wrote:
>     Hi all,
>     Has anyone noticed that `nginx -t' outputs an empty pid file while
>     the nginx process isn't running.
> no, but good catch!!!
I'm using 0.7.1.
>     I can only add
>      if [ ! -s $PID ]; then
>        rm -f $PID
>      fi
>     to the check-config section of my rc file at the moment.
> you dont need to, as far as i can tell. nginx just proceeds to overwrite 
> that file with the proper value when it starts up...
Yeah, ur right.

And I got some more info from debug.
With v0.7.1 running, when do another start, nginx will try to bind the 
addr for 5 times while the addr is in use, if the addr is still 
unavailable after 2.5s, then gives up. But the start command won't give 
any info, just quietly exit. So I thought nginx has started regularly, 
but in fact not that case.

So I always do process checking(check pid file) and warning in rc files, 
including nginx'.

The problem is nginx does give me an empty pid file.
> -jf
> --
> In the meantime, here is your PSA:
> "It's so hard to write a graphics driver that open-sourcing it would not 
> help."
> -- Andrew Fear, Software Product Manager, NVIDIA Corporation

More information about the nginx mailing list