question about Wants and unit start-up order

[grawity@xxxxxxxxx (Mantas Mikulėnas)]

On Fri, Mar 23, 2018 at 9:52 PM, Brian J. Murrell <brian at interlinx.bc.ca>
wrote:

> On Fri, 2018-03-23 at 21:45 +0200, Mantas MikulÄ?nas wrote:
> >
> > No, dependencies do not imply any specific ordering. (The only
> > exception is
> > when a .target wants/requires another unit.)
>
> That seems odd but I will leave that aside for a moment...
>
> > In other words, you will need to additionally list the same units in
> > After=, or in certain cases in Before=. (For example, named is a nss-
> > lookup
> > provider, so it should have "Before=nss-lookup.target", but
> > "After=named-setup-mdc.service".)
>
> That is the case:
>
> # systemctl show named-pkcs11.service | grep -ie ^before -e ^after
> Before=nss-lookup.target shutdown.target
> After=system.slice named-setup-rndc.service tmp.mount -.mount var.mount
> network.target systemd-journald.socket basic.target named-dhcp.service
>
> So it's still puzzling why they report out of order in the journal.
>
> > On another note, Wants=system.slice is *very* redundant â?? all system
> > services go into that slice anyway.
>
> That was output from systemctl show so it was probbaby just reflecting
> that, as the one above does.
>

Which systemd version do you run? In v232,

nss-lookup.target:Description=Host and Network Name Lookups
nss-user-lookup.target:Description=User and Group Name Lookups

-- 
Mantas MikulÄ?nas
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.freedesktop.org/archives/systemd-devel/attachments/20180324/a69fb224/attachment.html>