On Tue, Apr 26, 2016 at 5:52 PM, Reindl Harald <[email protected]> wrote:
> > > Am 26.04.2016 um 16:37 schrieb Mantas Mikulėnas: > >> On Tue, Apr 26, 2016 at 3:14 PM, george Karakou >> <[email protected] <mailto:[email protected]>> 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 <[email protected]>
_______________________________________________ systemd-devel mailing list [email protected] https://lists.freedesktop.org/mailman/listinfo/systemd-devel
