Bug#850435: starts daily, weekly, monthly targets at midnight

[Alexandre Detiste]

Hi,

I have a different proposal upstream that propose to get rid of
run-parts completely.
https://github.com/systemd-cron/systemd-cron/issues/47

I like it in some ways because run-parts gets in the way of proper logging
(it's exit-code is max of all process exit codes, error-mail is useless
& one has to investigate what went wrong);

but on the other way this means every daily|weekly|monthly jobs
will be started simultaneously.

Or maybe hopefully more & more packages would follow the way of APT's
apt-daily.timer
and /etc/cron.daily/ would then become an irrelevant empty shell.
see: /etc/cron.daily/apt-compat
see also: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=770440


BTW: ok for the initial "06:25, 06:47, 06:52"-like proposal;
coupled with persistent=true feature, this is a saner default for regular users.

> virtualized environment with many Debian systems.

These could easily deploy systemd config overides in /etc

> Different priorities I guess?

Yup, it's hard to please different people with differents needs.

Greetings,

Alexandre Detiste