On Wednesday, March 18, 2020 3:50:34 PM CET Zbigniew Jędrzejewski-Szmek wrote:
> On Wed, Mar 18, 2020 at 01:04:58PM +0100, Kamil Dudka wrote:
>
> > logrotate is a utility designed to simplify the administration of log
> > files on
a system which generates a lot of log files. It used to be
> >
Björn Persson writes:
> Kamil Dudka wrote:
>
>> The timer is currently not enabled on fresh installs to avoid
>> surprises (such as data lost)
>
> That's a surprise only if somebody expected that logs would be retained
> forever. Do people expect that?
Yes.
> Random programs failing because
Kamil Dudka wrote:
> The timer is currently not enabled on fresh installs to avoid surprises (such
> as data lost)
That's a surprise only if somebody expected that logs would be retained
forever. Do people expect that?
Random programs failing because the disk is full is a worse surprise in
my
On Wed, Mar 18, 2020 at 01:04:58PM +0100, Kamil Dudka wrote:
> logrotate is a utility designed to simplify the administration of log files
> on
> a system which generates a lot of log files. It used to be triggered by
> cron.
> The cron hook was unconditionally installed with logrotate but
On Wednesday, March 18, 2020 3:20:17 PM CET Dusty Mabe wrote:
> I guess it would be worth analyzing the problem space a bit:
>
> - in the past how many people do we think had logrotate installed and not
> cron?
I am worried more about automated provisioning rather than manual installations.
>
On 3/18/20 8:04 AM, Kamil Dudka wrote:
> logrotate is a utility designed to simplify the administration of log files
> on
> a system which generates a lot of log files. It used to be triggered by
> cron.
> The cron hook was unconditionally installed with logrotate but it took effect
>
logrotate is a utility designed to simplify the administration of log files on
a system which generates a lot of log files. It used to be triggered by cron.
The cron hook was unconditionally installed with logrotate but it took effect
only if a cron daemon was installed.
Starting with Fedora
