Date: Fri, 18 Jul 2008 13:45:10 +0200 From: Zbigniew Szalbot <z.szalbot@lcwords.com> To: freebsd-questions@freebsd.org Subject: Re: log size handling Message-ID: <48808246.10301@lcwords.com> In-Reply-To: <48807DC8.1050007@infracaninophile.co.uk> References: <487F2525.3030304@lcwords.com> <20080717072023.4b9e1d2f.wmoran@potentialtech.com> <487F2D9B.2010407@lcwords.com> <200807170904.26354.mario.lobo@ipad.com.br> <487F52EE.2050907@infracaninophile.co.uk> <4880748D.8030902@lcwords.com> <48807DC8.1050007@infracaninophile.co.uk>
next in thread | previous in thread | raw e-mail | index | archive | help
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
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?48808246.10301>