[systemd-devel] [PATCH] core: add startup resource control option

[Lennart Poettering]

On Thu, 22.05.14 08:42, Umut Tezduyar Lindskog (umut at tezduyar.com) wrote:

> 
> On Thu, May 22, 2014 at 2:18 AM, Lennart Poettering
> <lennart at poettering.net> wrote:
> > On Wed, 21.05.14 14:02, Umut Tezduyar Lindskog (umut at tezduyar.com) wrote:
> >
> >>
> >> Hi Cho,
> >>
> >> Do you have any technical reason why CPU shares are reverted back to
> >> the default value on "StartupFinished" but instead when the unit is in
> >> "activated" state?
> >
> > Well, the startup is only considered finished when the default target is
> > reached, which usually means that all units the target pulled in are
> > actually in activated state.
> 
> I believe you haven't had time to look at the rest of the thread. I
> tried to explain it a bit more here:
> http://lists.freedesktop.org/archives/systemd-devel/2014-May/019377.html

I did. But again, the StartupFinished signal is sent out after all jobs
have been processed, and the job queue is empty for the first time. But
this will only happen if *every single* job that was queued before
actually went though its "activating" state and is not in
"active". Hence there's really no point in waiting for any individual
unit's state change, since looking at the system-wide state is enough
and incorporates the individual unit's state changes

Lennart

-- 
Lennart Poettering, Red Hat