Beta Branch disable unneeded access_log and error_log directives in nginx.conf

On the same path:

there is nginx.pid file.

Is that the proper place for it?

 

Ok so now is it safe to delete all .log files from:

Code:

/usr/local/nginx/logs/

?

 

After restarting Nginx it is auto creating that files access.log and error.log on that path .....

It's not a problem but you may need to remove that function

 

Both have in front #

 

I just notice that even with the logs commented:

Code:

#access_log  logs/access.log combined buffer=128k flush=5m;
#error_log   logs/error.log warn;

at

Code:

/usr/local/nginx/conf/nginx.conf

After restart they are auto recreated and not only that also logs entries coming there

 

Then it will be better to change that edit from:

Code:

#access_log  logs/access.log combined buffer=128k flush=5m;
#error_log   logs/error.log warn;

to

Code:

access_log  logs/access.log off;
error_log   logs/error.log warn;

So we will get the access log off and the error log that we can't disable to log only warn messages

Thank you

 

Great thank you

For the error log i think we can use:

Code:

error_log /dev/null crit;

or maybe is better to use it like?

Code:

error_log stderr crit;

as the redirect to /dev/null does not work reliably since from version 0.7.53 /var/log/nginx/error.log is hardcoded to be used until the config file has been read....

Using /dev/null on systems where /var/log/nginx/* doesn't exist will cause nginx to quit.

 

What do you think George for that?

 

Ok thanks

But I think you must revert that fix from commenting the two lines to setting the access log to off; and what ever you like for the error log ...

So existing or new installations will have that...

Thank you!

 

Thank you

 

This is something we're going to have to manually add, right?

 

FYI - changing the access log to this will produce an error and an nginx restart fail.