There's a better way than all of these. ;-)
Check out cronolog, it'll automatically rotate files for you on either a
daily, monthly or yearly basis so you don't have to HUP the server
yourself after moving the log files..
http://www.ford-mason.co.uk/resources/cronolog/
-Dave
On Mon, Apr 09, 2001 at 09:04:31AM +0100, [EMAIL PROTECTED] wrote:
> Thanks for that. I did wonder about this method, but the first time I did
> this some of our log files were huge (>350MB). I've never been that
> knowledgeable about inodes, even though I've written C shells in the past. I
> think the penny has kind of dropped now. So basically you can move the files
> whilst they are being written to, because their inodes don't change. Then
> send a -SIGHUP to the main apache process to create new files (and inodes)
> in the original directory.
>
> I'll try this method the next time we move log files. Do I assume correctly
> that
> /etc/rc.d/init.d/httpd reload
>
> Does a graceful restart also?
______________________________________________________________________
Apache Interface to OpenSSL (mod_ssl) www.modssl.org
User Support Mailing List [EMAIL PROTECTED]
Automated List Manager [EMAIL PROTECTED]
