]] Steve Langasek > I'm also interested to know how systemd purports to handle the exceptional > cases, where a dependency on basic.target is not possible.
In general «you need to write the dependencies manually, then». As you're pointing out in your mail, that can get tricky to get right. > The nfs-common and rpcbind packages currently have no integration with > systemd, so they get the default behavior for SysV services in rcS.d: > WantedBy=sysinit.target, Before=sysinit.target. But there's nothing which > documents that sysinit.target is a precondition for remote-fs.target, so in > its current state, mounting of remote filesystems at boot is almost > certainly racy with systemd in Debian. That looks buggy or racy indeed. > What is the right way to make nfs-common behave correctly on startup with > systemd? Is there a reason that sockets.target is only a dependency of > basic.target, not of remote-fs-pre.target, which would enable use of > socket-based activation for fs helper daemons like those in nfs-common? rpcbind.socket would have a Before=rpcbind.service automatically (assuming we want socket activation). In addition, I imagine you'd want the various daemons to have After + Wants on rpcbind.service and rpcbind.service to be before=remote-fs-pre.target and WantedBy=remote-fs-pre.target. -- Tollef Fog Heen UNIX is user friendly, it's just picky about who its friends are -- To UNSUBSCRIBE, email to debian-ctte-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/m2bnzyk7m2....@rahvafeir.err.no
