12.04 Beta1, Wireless and unmounting network shares at shutdown

[daliz]

Hi,

I just installed 12.04 beta 1 to try out if some of the previous problems with network shares would be fixed and seems they are. I'm planning to install 12.04 LTS to several computers so that's why I'm testing in advance. But there is a new problem.

Situation is this:

I have a fileserver with several samba shares and a laptop that I use to access them. I mount the shares using /etc/fstab. Now when I shutdown the laptop, it takes minutes to shutdown. Only happens when I use wireless, on wired ethernet shutdown is fast. There seems to be a great amount of discussion of networking shutting down before mounted network shares are unmounted, and because of this the shares can't be unmounted and that's why it takes a long time. There are (OLD) reports of similar bugs in ubuntu launchpad too.

I looked into autofs and it probably would be a solution but nevertheless I think this issue should be looked into.

Thanks

[vw72]

A quick and dirty fix might be to alter the shutdown script to manually unmount the shares in question. Just a thought.

[daliz]

Yes when searching for this I read some suggestions for creating/modifying scripts to unmount the share. I'll probably try that if the final 12.04 still has this problem.

[Guest]

Hi,

having the same problem I found a solution in another forum that works perfectly for me (kudos to the original poster):

Edit /usr/bin/starkde script using e.g. Kate: "sudo kate /usr/bin/startkde". Immediately after the line saying "echo 'startkde: Shutting down...' 1>&2", insert a line saying "sudo umount -t cifs -a -f -l". Then, using visudo as root ("sudo visudo"), edit the sudoers file to allow the sudo command to execute umount without a password by adding the line (at the bottom of the file) "{username} ALL=(root) NOPASSWD: /bin/umount". Replace {username} with your username.

[james147]

kdesudo kate /usr/bin/startkde

Don't run gui programs as root, it can cause all sorts or problems.
Also, its better to use the systems shutdown mechanism to run scripts as root rather then editing a program designed to start a gui as a normal user then hacking sudo to let them run commands as root without a password.