Bug#1086710: reportbug: if-up.d/mountnfs is always a NO-OP and should be fixed or removed

[Athanasius]

On Tue, Nov 05, 2024 at 01:04:54PM +0000, Athanasius wrote:
>   Having:
> 
> 1. Disabled my custom /etc/dhcpcd.exit-hook script
> 2. `apt remove --purge initscripts`
> 3. Edited `/etc/fstab` to ensure the NFS mounts are `auto`, not
>   `noauto`.
> 
> The NFS mounts have now worked on two consecutive boots, apparently
> without issue.  So, I guess something with having `initscripts`
> installed *was* interfering with the systemd mechanisms for ensuring
> such mounts occur under DHCP (specifically when using dhcpcd).

  Ah, no, I spoke to soon.

  My /home/users is correctly mounted, but that is possibly as part of
the systemd integration of lightdm and that login process otherwise.

  My /mnt/tuesday/data0 NFS mount has *not* happened.

  And, indeed, I have this from the boot-time, before my user login:

2024-11-05T12:58:48.309395+00:00 emilia mount[5040]: mount.nfs: Network is unreachable
2024-11-05T12:58:48.309748+00:00 emilia systemd[1]: home-users.mount: Failed with result 'exit-code'.
2024-11-05T12:58:48.309856+00:00 emilia systemd[1]: Failed to mount home-users.mount - /home/users.
2024-11-05T12:58:48.310259+00:00 emilia mount[5042]: mount.nfs: Network is unreachable
2024-11-05T12:58:48.341092+00:00 emilia systemd[1]: mnt-tuesday-data0.mount: Failed with result 'exit-code'.
2024-11-05T12:58:48.341209+00:00 emilia systemd[1]: Failed to mount mnt-tuesday-data0.mount - /mnt/tuesday/data0.

i.e. systemd process failing to mount them, because it tried *before*
the network was properly configued.

-- 
- 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