[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Unified log handling



I notice that many (most) packages that have log files use savelog in
cron files instead of using logrotate.d. Is there a reason for this?
For example, /etc/cron.daily/squid includes the following:

	#    Rotate the squid.out logfile
	savelog -c 3 squid.out > /dev/null 2>&1

This deletes the fourth logfile, leaving only three or four days of log
files at any one time. If an admin wants to change this, he must grep
until he finds this line and figure out how to change it.

Logrotate, while nowhere near perfect, seems like a good solution to
the inconsistancy caused by packages rotating logs independently. I
want to reccomend its use as a Debian standard and figure out why many
maintainers have elected to use their own cron jobs instead.

Attachment: pgpTKVTGvdGbg.pgp
Description: PGP signature


Reply to: