Am Mittwoch, 2. Dezember 2020, 10:44:50 CET schrieb Thorsten Kukuk:

> Hi,

>

> we have quite some packages, which:

>

> 1. require logrotate and ship a logrotate configuration file

> 2. have a special directory in /var/log

> 3. never create a log file as they are controlled by systemd

>

> The reason the packages never write to the log file by default is, that

> they

 log to stdout/stderr and systemd/journald captures them.

>

> What should we do with such packages?

> Requiring logrotate, even if never used by default, is already a bad idea.

> It runs regular (so uses resources) without doing anything.

>

> Clobbering /var/log with special directories and files owned by special

> users will also only trigger actions, even if never used.

>

> What would be a good solution?

> I understand that some people may want to run this tools without control

> by systemd. But on the other side, in this cases the people have to adjust

> the configuration anyways.

>

> Maybe a good solution could be:

> - continue to ship the logrotate configuration file

> - only Recommend logrotate, not require it

> - let the admin create the configuration file and directory

Hello Thorsten,

the first thing i do on a server is to disable systemd-journal and use logrotate.

How are you going to look for a bug in the log if you don't know exactly what to look for?

So you're just looking for a pattern in the log.

That doesn't work with systemd.

This only works with text files.

And so systemd-journal is completely pointless for servers.

Please let it enable.

Regards

 Eric