Welcome! Log In Create A New Profile

Advanced

Is there any other way to trigger log reopen beside kill -USR1?

Liu Haifeng
January 22, 2013 10:30PM
Hi all,

In the common case, people rotate access log like this:

mv access.log access.XXX.log
kill -USR1 <nginx pid>

In my case, I have to do something like this:

if [ -f "access.log" ]; then
mv access.log access.20130121.log
fi

kill -USR1 <nginx pid>
mv access.log access.20130122.log

My goal is make the "current" log file named with the date pattern immediately, not after one day. Well, my script seams OK, but for a production script, I still worry about that is there any "unexpected" trigger can make nginx reopen the log file (I mean inside nginx, core and other modules)? Will there be any inside reopen action in the future?
_______________________________________________
nginx mailing list
nginx@nginx.org
http://mailman.nginx.org/mailman/listinfo/nginx
Subject Author Posted

Is there any other way to trigger log reopen beside kill -USR1?

Liu Haifeng January 22, 2013 10:30PM



Sorry, only registered users may post in this forum.

Click here to login

Online Users

Guests: 88
Record Number of Users: 6 on February 13, 2018
Record Number of Guests: 421 on December 02, 2018
Powered by nginx      Powered by FreeBSD      PHP Powered      Powered by MariaDB      ipv6 ready