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

Hi all,

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

mv access.log access.XXX.log
kill -USR1

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

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

kill -USR1
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?

This forum is not affiliated to the Ruby language, Ruby on Rails framework, nor any Ruby applications discussed here.

| Privacy Policy | Terms of Service | Remote Ruby Jobs