registry team mailing list archive

[Jan Lillelund <211631@xxxxxxxxxxxxxxxxxx>]

This is still a big issue on WiFi-enabled workstations. To put it into
perspective, we have upgraded from 8.04 LTS to 10.04 LTS and shutdown
still takes around 40 minutes for the 16 cifs mounts in FSTAB on four
workstations.  Users are seriously inconvenienced.

As hinted earlier, a workaround could be adding the K14-links to rc0.d
and rc6.d:

ln -s /etc/init.d/umountnfs.sh /etc/rc0.d/K14umountnfs.sh
ln -s /etc/init.d/umountnfs.sh /etc/rc6.d/K14umountnfs.sh

and deleting the equivalent S31umountnfs.sh link.

I see this as a stop-gap measure only until it has been fully tested and
verified.

However, as Max-Ulrich Farber also stated more than two years ago, the
full ramifications of this are not clear as I do not have the test cases
nor insight for that matter to determine that this does not adversely
affect something else.

Could someone please please take a look at this and have the issue
resolved.  This is not just an obscure technical issue but also affects
the image that ordinary mortal users have of Ubuntu.

-- 
Network is brought down before network filesystems are unmounted (CIFS timeout at shutdown)
https://bugs.launchpad.net/bugs/211631
You received this bug notification because you are a member of Registry
Administrators, which is the registrant for NULL Project.