On Tue, 19 Jul 2022 09:04:18 -0400
Tom Horsley <horsley1953(a)gmail.com> wrote:
On Tue, 19 Jul 2022 08:48:12 -0400
Ben Cotton wrote:
> (If you're fine with it running at midnight, you can use
> OnCalendar=daily)
So maybe if I just changed the "RandomizedDelaySec=12h" in the
existing unit to something like "RandomizedDelaySec=2h" it would run
some time between midnight and 2AM, which would probably be good
enough to keep it out of my way.
I had a similar issue, except that it was running immediately after
boot, performing lots of disk io when I wanted to do other things. I
changed the updatedb.timer file by adding
OnBootSec=3h
and changed the
AccuracySec=1h
instead of the 24 hours it had originally. That starts updatedb
sometime between 2 and 4 hours after boot. I don't know the internals
of systemd, but I assume that the accuracy means it only checks that
often.
And now it doesn't run immediately after boot.