В Wed, 23 Apr 2014 05:57:39 +0200
Lennart Poettering lenn...@poettering.net пишет:
Ah, OK, I think I got it now:
You have services that are to be started by timers that take a long time
to complete. THe timers have been configured to be persistent. If the
system comes up and the timestamp
On Wed, 23.04.14 21:01, Andrey Borzenkov (arvidj...@gmail.com) wrote:
В Wed, 23 Apr 2014 05:57:39 +0200
Lennart Poettering lenn...@poettering.net пишет:
Ah, OK, I think I got it now:
You have services that are to be started by timers that take a long time
to complete. THe timers
Hi,
On Wed, 23 Apr 2014 05:57:39 +0200
Lennart Poettering lenn...@poettering.net wrote:
[...]
Ah, OK, I think I got it now:
You have services that are to be started by timers that take a long time
to complete. THe timers have been configured to be persistent. If the
system comes up and
On Wed, 23.04.14 13:15, Leonid Isaev (lis...@umail.iu.edu) wrote:
Hmm, this sounds nasty. I wodner what we can do about it...
Maybe we should add a new setting PersistentExtraSec= to timer units or
so which allows delaying these kind of timers by an extra margin. Would
this work for
В Wed, 23 Apr 2014 20:30:35 +0200
Lennart Poettering lenn...@poettering.net пишет:
On Wed, 23.04.14 13:15, Leonid Isaev (lis...@umail.iu.edu) wrote:
Hmm, this sounds nasty. I wodner what we can do about it...
Maybe we should add a new setting PersistentExtraSec= to timer units or
Am 22.04.2014 07:07, schrieb Lennart Poettering:
On Fri, 18.04.14 11:34, Thomas Bächler (tho...@archlinux.org) wrote:
According to [1], when a persistent timer runs its service on boot, it
delays startup.
Humm? What precisely do you mean by delays bootup? Just scheduling a
timer unit
On Tue, Apr 22, 2014 at 9:37 AM, Thomas Bächler tho...@archlinux.org wrote:
I'm
CC'ing the original reporter, maybe he can give more information.
I think you forgot to do that...
-t
___
systemd-devel mailing list
systemd-devel@lists.freedesktop.org
Am 22.04.2014 10:33, schrieb Tom Gundersen:
On Tue, Apr 22, 2014 at 9:37 AM, Thomas Bächler tho...@archlinux.org wrote:
I'm
CC'ing the original reporter, maybe he can give more information.
I think you forgot to do that...
Strange stuff - he is listed in CC in the mail I received, but his
Hi,
I'll try to answer all questions at once...
On Tue, 22 Apr 2014 09:37:29 +0200
Thomas Bächler tho...@archlinux.org wrote:
Am 22.04.2014 07:07, schrieb Lennart Poettering:
Humm? What precisely do you mean by delays bootup? Just scheduling a
timer unit should have about zero
On Tue, 22.04.14 12:13, Leonid Isaev (lis...@umail.iu.edu) wrote:
Am 22.04.2014 07:07, schrieb Lennart Poettering:
Humm? What precisely do you mean by delays bootup? Just scheduling a
timer unit should have about zero effect on boot times... If it does
this would be a bug.
This is
On Fri, 18.04.14 11:34, Thomas Bächler (tho...@archlinux.org) wrote:
According to [1], when a persistent timer runs its service on boot, it
delays startup.
Humm? What precisely do you mean by delays bootup? Just scheduling a
timer unit should have about zero effect on boot times... If it does
11 matches
Mail list logo
