Is there any way other than killing/restarting the nginx processes? Am asking this because it seemed to me that nginx shouldn't need to be restarted for it to use the new log file, if I didn't read the wiki wrongly.<br>
<br>Ray.<br><br><div class="gmail_quote">On Tue, Sep 1, 2009 at 10:11 AM, Jim Ohlstein <span dir="ltr"><<a href="mailto:jim@ohlste.in">jim@ohlste.in</a>></span> wrote:<br><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
<div><div></div><div class="h5">Ray wrote:<br>
<blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
Am trying to configure for logfile rotation using logrotate with nginx (0.7.61). As the logrotate script runs, the old logfile is renamed and a new one is created, but nginx still writes to the old (renamed) logfile even with open_log_file_cache set to off according to <a href="http://wiki.nginx.org/NginxHttpLogModule#open_log_file_cache" target="_blank">http://wiki.nginx.org/NginxHttpLogModule#open_log_file_cache</a><br>
<br>
Is there anything that I'm missing out?<br>
<br>
Ray.<br>
</blockquote></div></div>
kill -USR1 `cat /path/to/nginx.pid`<br>
<br>
</blockquote></div><br>