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
Thorsten Kukuk, Distinguished Engineer, Senior Architect SLES & MicroOS
SUSE Software Solutions Germany GmbH, Maxfeldstr. 5, 90409 Nuernberg, Germany
Managing Director: Felix Imendoerffer (HRB 36809, AG Nürnberg)