Bug#870361: systemd: after/before is ignored

Michael Biebl biebl at debian.org
Tue Aug 1 14:38:01 BST 2017


Am 27.07.2017 um 17:23 schrieb Vladki:
> Package: systemd
> Version: 232-25+deb9u1
> Severity: normal
> 
> Dear Maintainer,
> 
> I wanted to create my own systemd unit to mount encrypted fs, and needed
> to ensure that it starts after the networking is fully up, and before
> zfs and samba starts. After many experiments with
> after/before/wants/requires/wantedBy/requiredBy, I got to a partial
> succes with sequence: network-online.target (dhclient up) -> custom_mount_end.service
> -> zfs.target.
> 
> But smbd is still starting too early. By default it has After=nmbd.service, and
> nmbd has After=network-online.target. But the reaility is that smbd is
> started in parallel with dhclient, while nmbd correctly waits for
> dhclient to set up networking.
> 
> I tried to add After=zfs.target and Wants=zfs.target to smbd, call
> systemctl reeenable smbd, reboot. But it still starts too early.
> 
> Either the documentation is not clear enough or the options After and
> Before are not working as they should.

I'm pretty sure After/Before works correctly.
Can you please be more specific which units should be ordered against
each other in what way.


-- 
Why is it that all of the instruments seeking intelligent life in the
universe are pointed away from Earth?

-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 833 bytes
Desc: OpenPGP digital signature
URL: <http://lists.alioth.debian.org/pipermail/pkg-systemd-maintainers/attachments/20170801/a4d6a84f/attachment.sig>


More information about the Pkg-systemd-maintainers mailing list