This is still a bug, but it's not in sysvinit. Renaming S31umountnfs to
K31umountnfs might help not because S31umountnfs is called with "start"
(everything is called with "stop" for rc0.d and rc6.d), but because it
simply happens earlier in the shutdown sequence.
This is most probably a problem with the NetworkManager shutdown timing.
This is discussed in bug 211631.
** Changed in: sysvinit (Ubuntu)
Status: Confirmed => Fix Released
--
Symlinks for umountnfs / sendsigs wrong: hang on shutdown / reboot
https://bugs.launchpad.net/bugs/42121
You received this bug notification because you are a member of Ubuntu
Bugs, which is a direct subscriber.
--
ubuntu-bugs mailing list
[email protected]
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
