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

[Julian Andres Klode]

On Fri, Jan 06, 2017 at 02:29:19PM +0100, Marc Haber wrote:
> 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.

That's sort of funny, because systemd likes to move timers closer
together (with AccuracySec) in order to minimize the time where the
system is not idle, or something like that :)

Different priorities I guess?

-- 
Debian Developer - deb.li/jak | jak-linux.org - free software dev
                  |  Ubuntu Core Developer |
When replying, only quote what is necessary, and write each reply
directly below the part(s) it pertains to ('inline').  Thank you.