17 Apr
2014
17 Apr
'14
8:40 p.m.
On Thu, Apr 17, 2014 at 9:31 PM, Thomas Bächler <thomas@archlinux.org> wrote:
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.
When the timer fires it adds a start job to the manager. Type=idle services wait for the manager job list (not the transaction job list) to empty. Maybe Type=idle should be changed to trigger when its transaction completes.