[systemd-devel] Require a systemd.unit to finish completely before other services(units) are started
Reindl Harald
h.reindl at thelounge.net
Tue Apr 26 14:52:33 UTC 2016
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?
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 181 bytes
Desc: OpenPGP digital signature
URL: <https://lists.freedesktop.org/archives/systemd-devel/attachments/20160426/2cf7a1b0/attachment.sig>
More information about the systemd-devel
mailing list