Hi all,
I'm trying to set some kind of log rotation scheme up on a new installation of
Apache 1.3.6 and I've tried 2 different programs to do this, however, I see that
every line piping the logging in the apache config files makes a permanent
process that stays running even when nothing is being logged to that particular
log file.
I tried a small program named logrotor and I thought it was that program doing
this, but then I tried the rotatelogs from the apache distribution and the same
thing happen, there is always a process with a "/bin/sh -c" calling the actual
program and an other process for the program itself.
Why are these processes remaining and not terminating once the logging entry to
the log file is written?
Why is the "/bin/sh -c" call being made and not the program directly as we have
it in the config files?
Is this the way the piping works on apache?
I'm also looking into the RedHat logrotate util which also can delete old logs
and do a few other things, but will it work right under DU4.0b??
Is there a better way to handle this log rotation available out there?
What I would like to do is something like the syslog.dated system, which stores
the log files in a dated directory, separating the bunch of logs of the same
period from the other logs being created or the old ones from previous periods.
This would allow automatic deletion of the old logs by getting rid of the whole
folder that contains them, just like syslog does automatically.
Has anyone thought of that yet?
--
Didier Godefroy
mailto:dg_at_ulysium.net
Received on Wed Jun 30 1999 - 21:58:59 NZST