I tried adding x-systemd.requires=NetworkManager.service in fstab and it works when starting the system up, but it still makes me wait 30 minutes when shutting down.
2015-09-10 12:08 GMT-03:00 Javier Ayres <javieray...@gmail.com>: > What I mean is to start the NFS mounting service after NetworkManager, > which would also mean to stop it before NetworkManager, right? I didn't > know network.target is the service that mounts NFS shares, in which case > now I understand that what I'm asking is what you explained that is not > possible. > > I guess I could mount and unmount the drive with a custom script in the > meantime. Thanks for your support! > > 2015-09-10 11:50 GMT-03:00 Michael Biebl <bi...@debian.org>: > >> Am 10.09.2015 um 16:19 schrieb Javier Ayres: >> > Trying to manually unmount the drive with the network down blocks (with >> CPU >> > at 100%) indefinitely, or so it appears. I waited 40 minutes and then >> > canceled it because I had to go. >> >> This is probably a problem on its own. >> >> > Can't the service which mounts/unmounts NFS (not sure which one that >> is) be >> > put after NetworkManager? >> >> I guess you mean *before*. But well, as I tried to explain, currently >> that doesn't work in Debian since we can't order NetworkManager.service >> before network.target. >> >> Doing that should ensure that NetworkManager.service is stopped after >> the NFS shares have been unmounted. >> >> >> >> >> -- >> Why is it that all of the instruments seeking intelligent life in the >> universe are pointed away from Earth? >> >> > > > -- > Javier Ayres > -- Javier Ayres
