question about Wants and unit start-up order

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



If I have:

Wants=system.slice nss-lookup.target named-setup-rndc.service

in named-pkcs11.service, so shouldn't mean that named-pkcs11.service
will be started up before the nss-lookup.target is Reached/Started?

That doesn't seem to be the case on my system:

Mar 23 09:44:03 server.interlinx.bc.ca systemd[1]: Reached target User and Group Name Lookups.
Mar 23 09:44:03 server.interlinx.bc.ca systemd[1]: Starting User and Group Name Lookups.
Mar 23 09:47:35 server.interlinx.bc.ca systemd[1]: Starting Berkeley Internet Name Domain (DNS) with native PKCS#11...
Mar 23 09:47:42 server.interlinx.bc.ca systemd[1]: Started Berkeley Internet Name Domain (DNS) with native PKCS#11.

Am I misunderstanding what systemd is trying to tell me above?  Is it
not saying that the nss-lookup.target was reached (and therefore
services that depend on it can go ahead) before the DNS service was
actually even started?

If I am misunderstanding, is there a better way to understand the order
that units were started in than looking at the journal?

Cheers,
b.
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 488 bytes
Desc: This is a digitally signed message part
URL: <https://lists.freedesktop.org/archives/systemd-devel/attachments/20180323/05dcb6a9/attachment.sig>


[Index of Archives]     [LARTC]     [Bugtraq]     [Yosemite Forum]     [Photo]

  Powered by Linux