On Mon, Mar 1, 2010 at 2:25 PM, MarkMT <nginx-forum@nginx.us> wrote:

> I tried renaming the file and restarting - no access.log file was created
> on subsequent accesses.
>
> Other thoughts?
>

On linux, lsof -c nginx (as root) should tell you if nginx has the logfiles
opened.
Also, "strace" may help in understanding whether it's a file permission
problem (actually I believe it isn't, nginx should not start if it can't
write to its logfiles).
Also, you may have some stale processes, so stop nginx, and then check via
ps aux if you have any left.. if you do kill them via killall nginx.

Hope this helps!
_______________________________________________
nginx mailing list
nginx@nginx.org
http://nginx.org/mailman/listinfo/nginx