Bug 1115445 - logwatch: migrate from cron to systemd timers
logwatch: migrate from cron to systemd timers
Classification: openSUSE
Product: openSUSE Tumbleweed
Classification: openSUSE
Component: Basesystem
x86-64 openSUSE Factory
: P3 - Medium : Normal (vote)
: ---
Assigned To: Christian Vögl
E-mail List
Depends on:
Blocks: 1115430
  Show dependency treegraph
Reported: 2018-11-09 14:49 UTC by Kristyna Streitova
Modified: 2019-08-12 08:49 UTC (History)
2 users (show)

See Also:
Found By: ---
Services Priority:
Business Priority:
Blocker: ---
Marketing QA Status: ---
IT Deployment: ---
christian.voegl: needinfo? (trenn)


Note You need to log in before you can comment on or make changes to this bug.
Description Kristyna Streitova 2018-11-09 14:49:09 UTC
This bug is part of TRACKERBUG bug#1115430.

Based on fate#323635 (Reduce usage of cron package in favor of systemd timers) we would like to minimize the number of packages that use cron in favour of systemd timers.

It seems that your package uses cron. Please take a look at it and evaluate if it's possible to migrate your package to use systemd timers without impacting behaviour. If it's not possible, please write down the reason.

Please note that by default, services are not enabled when the package is installed. You probably want your service to be enabled by default so you should create a submit request on systemd-presets-branding-openSUSE package, modifying default-openSUSE.preset file by adding "enable your_service_name.service".
Comment 1 Kristyna Streitova 2018-11-16 13:46:19 UTC
(In reply to Kristyna Streitova from comment #0)
> ... modifying default-openSUSE.preset file by adding "enable
> your_service_name.service".

A small correction: it should be "enable your_timer.timer" of course. See [1] for more information about systemd timers packaging. Feel free to enhance this wiki page. Thanks!

[1] https://en.opensuse.org/openSUSE:Systemd_packaging_guidelines#Systemd_timers
Comment 2 Christian Vögl 2019-08-12 08:49:20 UTC
Package is now migrated in factory