On Thu, 17 Apr 2014 21:31:07 +0200
Thomas Bächler tho...@archlinux.org wrote:
[...]
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
Am 21.04.2014 18:56, schrieb Leonid Isaev:
On Thu, 17 Apr 2014 21:31:07 +0200
AFAIU, there are 2 real issues here:
1. We hook to the boot process a bunch of disk-intensive operations which did
not belong there in the 1st place.
2. Even if a boot delay for timers is implemented or the behavior
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
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
On Thu, 17 Apr 2014 21:31:07 +0200
Thomas Bächler tho...@archlinux.org wrote:
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
On Thu, Apr 17, 2014 at 9:31 PM, Thomas Bächler tho...@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
6 matches
Mail list logo
