On Mon, Nov 04, 2024 at 12:52:44PM +0000, Athanasius wrote: > Obviously this bug can be closed.
Having checked more into why mountnfs.service is masked, I'm not so sure. Unless there's a flaw in my understanding, the situation is: 1. There is no actual systemd mountnfs.service. 2. This instead refers to the SysV init script /etc/init.d/mountnfs.sh 3. The systemd invocation of this became masked in Debian buster (I keep /etc under git, and the only commit for the masking symlink to /dev/null is from my Stretch>Buster upgrade). See /var/lib/dpkg/info/initscripts.postinst for the code that performs this masking. Search for `INITSCRIPTS`. 4. With it masked, that lsb-init function makes invocation of if-up.d/mountnfs a no-op. 5. With it UNmasked, the check in the first code in if-up.d/mountnfs causes it to be a no-op. Conclusion: if-up.d/mountnfs is now non-functional, should be removed, and cannot in any way, shape or form be relied upon for invoking NFS mounts when a NIC has been brought up. dhcpcd should not be relying on it. I'll now see if I can find which part of *systemd* is meant to take care of this instead. A reminder. In my use case *something* was performing the NFS mounts perfectly fine *when I had a static IPv4 setup*. Moving from static to DHCP is what's brought this to light. -- - Athanasius (he/him) = Athanasius(at)miggy.org / https://miggy.org/ GPG/PGP Key: https://miggy.org/gpg-key "And it's me who is my enemy. Me who beats me up. Me who makes the monsters. Me who strips my confidence." Paula Cole - ME
