I think your analysis is incorrect.
S31umountnfs.sh in rc0 or rc6 is in fact called with the "stop" argument.
Moving it to K31 just makes it be called sooner in the shutdown process, which
is wrong.
The samba unmount issue you experience is probably bug 211631 (network dies
before the cifs files
** Changed in: sysvinit (Ubuntu)
Sourcepackagename: None => sysvinit
--
unmountnfs.sh wrong call
https://bugs.launchpad.net/bugs/315003
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu
that is a solution, but you start the unmount, so this is a
cleaner/logical solution.
--
unmountnfs.sh wrong call
https://bugs.launchpad.net/bugs/315003
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
ubuntu-
It's the same on my system, there is S31umountnfs.sh symlinks in rc0.d
and rc6.d. An alternative solution would be to replace them with
K31umountnfs.sh symlinks.
** Changed in: ubuntu
Status: New => Confirmed
--
unmountnfs.sh wrong call
https://bugs.launchpad.net/bugs/315003
You received
** Attachment added: "working solution to the problem."
http://launchpadlibrarian.net/21003146/umountnfs.sh
--
unmountnfs.sh wrong call
https://bugs.launchpad.net/bugs/315003
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu
