Re: Sending nginx errors to syslog but fuser -u still shows error file open by nginx

Ok, I understand what is happening now, thank you! On Wed, Apr 20, 2016 at 11:52 AM, Maxim Dounin wrote: > Hello! > > On Wed, Apr 20, 2016 at 09:24:52AM -0400, CJ Ess wrote: > > > I've tried putting this directive into the nginx config file in both the > > main and html

Re: Sending nginx errors to syslog but fuser -u still shows error file open by nginx

Hello! On Wed, Apr 20, 2016 at 09:24:52AM -0400, CJ Ess 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

Re: Sending nginx errors to syslog but fuser -u still shows error file open by nginx

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 < rpapro...@fearnothingproductions.net> wrote: > Have you done a full restart (not a

Sending nginx errors to syslog but fuser -u still shows error file open by nginx

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