Changing the S to K makes the nfs unmount happen earlier during the
shutdown process, which seems to solve this issue for some, but not for
me. However, this bug was fixed a better way in Debian, which should
solve the issue for all. See bug report and patch here:
http://bugs.debian.org/cgi-bin/b
I've hit this bug also I had thought it was just a general computer doesn't
want to shutdown issue
till I had a nfs mount on my laptop and it did the same
no vpn is being used here and moving the files from S to K did make it
shutdown right again
--
Looks like symlinks for umountnfs and umoutfs
I have the problem described in the duplicate of this bug (CIFS only,
not SMBFS or other types) and above. However, the workarounds posted
here do not solve the problem in my case - the computer still waits
30-60 seconds for each network connection to fail to shut down. Is
there any other way to
Though we'll fix this through upstart, and the init scripts will go away
** Changed in: sysvinit (Ubuntu)
Status: Unconfirmed => Confirmed
--
Looks like symlinks for umountnfs and umoutfs is wrong
https://launchpad.net/bugs/42121
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
** Changed in: Ubuntu
Sourcepackagename: None => sysvinit
--
Looks like symlinks for umountnfs and umoutfs is wrong
https://launchpad.net/bugs/42121
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
This is true, either we need to change rc0/6.d S??umountnfs to
K??umountnfs, or as I did, change /etc/init.d/umountnfs.sh to do the
same thing on both start and stop.
Ive just done this now, so I havent tested it, but someone please
CONFIRM this bug.
Thanks
--
Looks like symlinks for umountnfs
