Ubuntu
network-manager package

  1. Bug #113095
  2. Comment #3

Comment 3 for bug 113095

Revision history for this message
Daniel J Blueman (danielblueman) wrote : Re: nfs timeout on shutdown

I'm experiencing the same issue in Hardy and Intrepid (and before), with NFSv4 homedir and been bumping into this really a lot.

To see what's actually happening, change VERBOSE to 'yes' in /etc/default/rcS and boot without 'splash', as you'll already know; there is a problem/race with your suggested change - take rc6 (for reboot preparation) for example:

$ ls -1 /etc/rc6.d/S*
S01linux-restricted-modules-common
S15wpa-ifupdown
S20sendsigs
S30urandom
S31umountnfs.sh
S32portmap
S35networking
S40umountfs
S48cryptdisks
S59cryptdisks-early
S60umountroot
S85kexec
S90reboot

The umountnfs script won't (always) succeed until user processes (with open file handles) are killed with the 'sendsigs' script - but this also kills networkmanager, which brings the ethernet interface down.

There is a handy directory /lib/init/rw/sendsigs.omit.d/ which contains symlinks to processes which must not be killed here, so the true fix would be add the code to the NetworkManager init script, at the end of the start clause (taken from the portmap init script):

        mkdir -p /lib/init/rw/sendsigs.omit.d
        rm -f /lib/init/rw/sendsigs.omit.d/portmap
        ln -s /var/run/portmap.pid /lib/init/rw/sendsigs.omit.d/portmap

Patch attached. Works great here - please confirm there.