[systemd-devel] Require a systemd.unit to finish completely before other services(units) are started

[Mantas Mikulėnas]

On Tue, Apr 26, 2016 at 5:52 PM, Reindl Harald <h.reindl at thelounge.net>
wrote:

>
>
> Am 26.04.2016 um 16:37 schrieb Mantas Mikulėnas:
>
>> On Tue, Apr 26, 2016 at 3:14 PM, george Karakou
>> <mad-proffessor at hotmail.com <mailto:mad-proffessor at hotmail.com>> wrote:
>>
>>     It's actually NetworkManager-dispatcher whose actual job is -if i am
>>     not mistaken- to run some scripts after NetworkManager main process.
>>     Though i have configured NetworkManager-wait-online too but
>>     systemd's parallelizazion is unbeatable: services are started in
>>     parallel and i see other services that i have ordered after
>>     dispatcher finishing starting and dispatcher is still exec'ing my
>>     scripts.
>>
>> Because systemd _does not know_ that the dispatcher daemon is doing
>> something in the background.
>>
>> You seem to be convinced that systemd is doing some trickery to
>> parallelize NM. Meanwhile it's the exact opposite
>>
>
> and what is the solution for such cases when it does and can not know but
> continues fire up parallel things which need proper ordering?
>
> or in other words how is "NetworkManager-wait-online" supposed to do the
> job it's name implies in case of a systemd environment?
>

Well, I actually expected for NetworkManager-wait-online to block until all
the "dispatcher" hooks finished...

-- 
Mantas Mikulėnas <grawity at gmail.com>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.freedesktop.org/archives/systemd-devel/attachments/20160426/cb42e38b/attachment-0001.html>