On Tue, Jan 11, 2000 at 10:05:52PM +0000, Steve Haslam wrote:
> > So to my way of thinking, no logs should be rotated if there isn't a
> > logrotate package installed. If there is one or not is up to the
> > administrator, though I strongly suggest one...
>
> So all packages that rotate their logs "manually" using savelog should
> convert to logrotate... hmm...
>
> Also, there's the fact that if I installed logrotate in order to get
> package X's logs rotated, why should I suddenly get package Y's logs
> rotated as well? I don't think the presence/absence of a package as
> this type of configuration is a good idea.
Let's say cron's maintainer decides to convert
/etc/cron.daily/standard to use logrotate, in concordance with the
current policy manual. So he makes cron Depend on logrotate,
requiring logrotate to become an important package (cron is
important). Now logrotate will basically be present on every
up-to-date Debian system and packages which used to use savelog in
their crontabs can start using logrotate (which they could do
already). As long as the /etc/logrotate.d files they create exactly
match the current savelog settings in the crontab files, sysadmins who
haven't touched the crontab won't notice a difference, and ones who
have will be prompted as to whether to install the new crontab (as
it's a conffile). And caveat emptor for sysadmins who blindly ignore
any local changes they have made when upgrading packages.
So this argument is basically spurious as long as we make logrotate
important.
Julian
--
=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-
Julian Gilbey, Dept of Maths, QMW, Univ. of London. [EMAIL PROTECTED]
Debian GNU/Linux Developer, see http://www.debian.org/~jdg
Donate free food to the world's hungry: see http://www.thehungersite.com/
