log size handling

Zbigniew Szalbot z.szalbot at lcwords.com
Fri Jul 18 11:45:13 UTC 2008


Hello,

Matthew Seaman:

> Correct.  Although you may want to add '30' as the 8th field -- that means
> 'send signal 30 (SIGUSR1) to apache instead of SIGHUP' -- SIGUSR1 causes
> apache to do a graceful restart rather than abruptly killing and restarting
> everything: http://httpd.apache.org/docs/2.2/stopping.html
> 
> You'll need to experiment though -- if your user HTTP connections are 
> long-lived, you can end up with apache appending data to a rotated logfile
> that it still has an open file descriptor on.  The file will be unlinked
> once the gzip compression has run.  Now, writing to an unlinked file is
> allowed under Unix, but once that apache child process terminates and 
> releases the descriptor the  data will disappear into the ether,  so you
> can lose log entries.

Thank you very much Matthew! Just one final question. When the apache 
child process finally terminates, will apache start logging to a new 
log? Or will it be writing into the ether until it gets restarted?

Thanks again! I appreciate your help.

-- 
Zbigniew Szalbot
www.LCWords.com


More information about the freebsd-questions mailing list