On 01/16/14 07:09, Tom Horsley wrote: >> Well, you could always make a wrapper around a shutdown command and use "umount -f" as in "force". >> > Something like that might work if this bugfix has made it into > the current kernel (it probably has, we're on 3.12 now): > > https://bugzilla.redhat.com/show_bug.cgi?id=980088 > > But what I'd really need is a new systemd unit that > umount depends on that could run first and umount -f > all the NFS filesystems in the background, then umount -l > them for good measure (because I've seen -f take > forever to timeout as well :-). That way I wouldn't > need an alias for every possible shutdown command. Well, I suppose you could always work on your own systemd unit to do that. I certainly wouldn't want it as a default on any of my systems. I've got a fairly old/slow NFS server on my network and when large transfers are going on it can appear to be hung. I'd be concerned that doing this as a default action would result in transfers being terminated and data being lost/corrupted. Unless there are others than yourself using the system you wouldn't need an alias for every possible shutdown command. :-) :-) -- Getting tired of non-Fedora discussions and self-serving posts -- users mailing list users@xxxxxxxxxxxxxxxxxxxxxxx To unsubscribe or change subscription options: https://admin.fedoraproject.org/mailman/listinfo/users Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct Guidelines: http://fedoraproject.org/wiki/Mailing_list_guidelines Have a question? Ask away: http://ask.fedoraproject.org
