On Mon, Feb 08, 1999 at 11:16:35AM +0100, Harald Hanche-Olsen wrote:
> You may have to change some path names. Also, note that this job
> keeps the last 10 log files uncompressed, for ease in checking the
> lateste logs. I run cyclog with the arguments -s304000 -n30; you may
> have to adjust these parameters. With a setup like this, there is
> always a risk of losing log information if activity suddenly
> skyrockets.
I've actually been wondering about this for some time now: With syslog and
nightly log rotation, we always have at least 7 days (or whatever is the
rotational cycle) worth of logs to look at. Often this is useful if we want
to track messages a few days old. With cyclog, if there is a lot of
activity suddenly, we may end up with logs a couple of days old. Has anyone
worked out a scheme of making sure that cyclog's logs are kept for at least
x number of days? What would be nice is if cyclog had some way of signaling
to us that it had rotated a log, and we could save that away in a
directory. We could then have a cron job cleaning this directory to remove
log files more than x days old. This way, cyclog can rotate logs as quickly
as it likes, but we control when they are removed.
--
Anand
System Administrator
Africa Online Ltd
http://www.anand.org
