Re: dpkg status history...how much is too much?

[montefin <montefin@finux.com>]

Colin,

A perfect answer. Clear. To the point. Actionable.

Thank you,

montefin


Colin Watson wrote:
> 
> montefin <montefin@finux.com> wrote:

> >Does dpkg need all that status history? And if not, must I monitor it
> >myself, or does dpkg have a self-cleansing method that is somehow not
> >being invoked here?
> 
> /etc/cron.daily/standard does the log rotation here; you could decrease
> the number 7 in the relevant 'savelog' line, though at the expense of
> having to put up with being asked if you want to replace that script
> every time you upgrade cron. (Hmm, it really ought to use logrotate
> instead ...)
> 
> I'd advise you to keep some status history around; dpkg doesn't need it,
> but it always seems to be right after I delete something like that that
> *I* need it. If you find a week's worth excessive, though, then go ahead
> and turn the setting down.
> 
> available-old and status-old are created by dpkg when updating its
> database; I doubt you can do very much about that.
> 
> --
> Colin Watson                                     [cjw44@flatline.org.uk]