2014/1/15 Tom Horsley <horsley1953@xxxxxxxxx>
Not when it was dead easy to change the init script to stick
an '&' on the end of the umount command, it didn't wait then, and
even when you forgot to do that, it didn't take hours to
timeout like systemd does.
But of course, according to the devs, it is a common myth that
systemd isn't scriptable, so obviously there is a simple way to
change this behavior, right? (Though I've been poking through
the source and it sure looks to me like the only way to change
this is to rebuild from source and check fstype for "nfs" to
prevent it from trying forever to umount it).
Try to add the mount option "_netdev", it should schedule the mount/umount after/before the network.
-- 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
