Yes, I went as far as to stop nginx altogether, manually verify there are
no nginx processes running, then start it again and it opens the error log
first thing.

On Wed, Apr 20, 2016 at 9:51 AM, Robert Paprocki <
rpaprocki@fearnothingproductions.net> wrote:

> Have you done a full restart (not a reload)? I would imagine the master
> process needs to flush everything out.
>
> > On Apr 20, 2016, at 06:24, CJ Ess <zxcvbn4038@gmail.com> wrote:
> >
> > I've tried putting this directive into the nginx config file in both the
> main and html sections:
> >
> > error_log syslog:server=127.0.0.1,facility=local5 error;
> >
> > The file tests fine and reloads without issue, however if I do fuser -u
> on the error file (which is the same one used by syslog) I see that every
> nginx process has it open. Is there anyway to be sure that errors are being
> written by syslog and not the nginx process itself?
> >
> >
> > _______________________________________________
> > nginx mailing list
> > nginx@nginx.org
> > http://mailman.nginx.org/mailman/listinfo/nginx
>
> _______________________________________________
> nginx mailing list
> nginx@nginx.org
> http://mailman.nginx.org/mailman/listinfo/nginx
>
_______________________________________________
nginx mailing list
nginx@nginx.org
http://mailman.nginx.org/mailman/listinfo/nginx