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

[Marc Haber]

Package: systemd-cron
Version: 1.5.4-2
Severity: wishlist

Dear Maintainer,

thanks for providing this compatibility layer to help transition from
a cron daemon to systemd timers. Using run-parts in the .service units
prevents all items of a daily|weekly|monthly cron job from starting at
once.

However, daily|weekly|monthly are started together at midnight, while
the classic crond/anacron setup starts them in a staggered way which
helps keeping the load spike low.

Please consider giving times inside the .timer units that resemble the
06:25, 06:47, 06:52 staggering that the normal vixie cron does. Also,
please consider mentioning RandomizedDelaySeconds in a README file so
that people get reminded that we now have a possibility to spread the
load of the daily cron jobs in a virtualized environment with many
Debian systems.

Greetings
Marc


-- Package-specific info:
-- output of systemd-delta

-- System Information:
Debian Release: stretch/sid
  APT prefers unstable
  APT policy: (500, 'unstable')
Architecture: amd64 (x86_64)

Kernel: Linux 4.9.0-zgsrv20080 (SMP w/2 CPU cores; PREEMPT)
Locale: LANG=en_DK.utf8, LC_CTYPE=en_DK.utf8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)

Versions of packages systemd-cron depends on:
ii  init-system-helpers  1.46
ii  libc6                2.24-8
pn  python3:any          <none>
ii  systemd-sysv         232-8

Versions of packages systemd-cron recommends:
ii  exim4-daemon-light [mail-transport-agent]  4.88-2

systemd-cron suggests no packages.

-- no debconf information