[arch-general] Many timers now running at boot. How to make them run later?

[Christian Hesse]

"David C. Rankin" <drankinatty at suddenlinkmail.com> on Thu, 2019/11/21 04:08:
> [...]
>
>   What is the best way to modify this scheme to prevent, e.g.
> logrotate.time, man-db.timer and shadow.timer all trying to run on boot?
> I'd rather set them up to run a 5:00 localtime as I would with cronnie. But
> I do want to use the systemd timer, so what is the best way to configure
> the systemd timer to schedule these things to run at a convenient time
> instead of all firing on boot?

I've created systemd configuration overlay snippets for this, for example
/etc/systemd/system/man-db.timer.d/RandomizedDelaySec.conf:

[Timer]
RandomizedDelaySec=30min

Create a file for every timer you want to delay.
-- 
main(a){char*c=/*    Schoene Gruesse                         */"B?IJj;MEH"
"CX:;",b;for(a/*    Best regards             my address:    */=0;b=c[a++];)
putchar(b-1/(/*    Chris            cc -ox -xc - && ./x    */b/42*2-3)*42);}
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 488 bytes
Desc: OpenPGP digital signature
URL: <https://lists.archlinux.org/pipermail/arch-general/attachments/20191121/d6545442/attachment.sig>