[arch-general] On-boot delay due to timer units

[Thomas Bächler]

Am 17.04.2014 20:56, schrieb Leonid Isaev:
> Hi,
> 
> Since anacron jobs were replaced with timers, I am seeing a noticeable delay
> before agetty prompt appears on machines which were unused for some time (due
> to update/man-db timers starting up simultaneously).
> 
> TLDR: Anacron inserts a random delay between boot and running the jobs, so is
> it possible to simulate this behavior by including e.g. "OnBootSec=..." in the
> timers at next update? Or is this option incompatible with OnCalendar?

OnBootSec would cause the timers to always run on boot, no matter how
much time has passed, which is not what we want.

I don't think it is a problem that the timers run on boot, but rather
that they delay Type=idle units, like agetty. From what the
documentation says, there should not be any delay:

"Behavior of idle is very similar to simple; however, actual execution
of the service binary is delayed until all jobs are dispatched."

I am confused why get a delay here.

I think another solution in systemd would be introducing a holdoff time:
Instead of running immediately on boot, the timer should be scheduled
for boot+5min.

This requires some investigation - sorry, I don't have a quick solution
right now.

-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 901 bytes
Desc: OpenPGP digital signature
URL: <http://mailman.archlinux.org/pipermail/arch-general/attachments/20140417/40182ca8/attachment.asc>