Le mercredi 02 décembre 2020 à 15:07 +0100, Michael Ströder a écrit :
On 12/2/20 1:23 PM, Frederic Crozat wrote:
Le mercredi 02 décembre 2020 à 12:11 +0000, Martin Wilck a écrit :
On Wed, 2020-12-02 at 10:44 +0100, Thorsten Kukuk wrote:
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
Maybe like this:
Package the logrotate stuff separately (e.g. as $X-logrotate) and use
Requires: ($X and logrotate) Supplements: ($X and logrotate)
and
Recommends: ($X-logrotate unless systemd)
which means it will never be recommended. I'd go with
Recommends: ($X-logrotate unless systemd-logger)
AFAICS systemd-logger is related to syslog socket. But Thorsten was talking about logrotate for custom log *files*.
No, systemd-logger is just a package which contains /var/log/journal (to cause systemd journal to be persistent) and has the needed provides to allow uninstallation of other syslogs. -- Frederic Crozat Release Manager SUSE Linux Enterprise SUSE