Symlinks for umountnfs / sendsigs wrong: hang on shutdown / reboot
Bug #42121 reported by
PC
This bug affects 22 people
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
sysvinit (Debian) |
Fix Released
|
Unknown
|
|||
sysvinit (Ubuntu) |
Fix Released
|
Medium
|
Unassigned | ||
Bug Description
It looks like the symlinks for S31umountnfs and S40umountfs in rc0.d and rc6.d are wrong because if you access an nfs mount over a VPN, then the machine fails to shut down unless you manually umount the nfs before going to init 0 or init 6.
I changed the S31umountnfs and S40umountfs to K31umountnfs and K40umountfs and the problem seems to have gone.
Related branches
Changed in sysvinit: | |
status: | Unknown → Fix Released |
Changed in sysvinit (Ubuntu): | |
assignee: | Martin Pitt (pitti) → nobody |
Changed in sysvinit (Debian): | |
status: | Fix Released → Confirmed |
status: | Confirmed → Fix Released |
Changed in sysvinit (Ubuntu): | |
status: | New → Confirmed |
To post a comment you must log in.
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