network-manager is stopped too soon at shutdown, before CIFS unmounts
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
network-manager (Ubuntu) |
New
|
Undecided
|
Unassigned |
Bug Description
I think I already reported that bug but I couldn't find it in launchpad, so I'm creating a new one. I use network-manager on my laptop to manage DHCP for wired and wireless connections. In my fstab, I have a couple of CIFS shares with the "noauto, users" switches that allow me to mount a share at any time, after startup. However, when I shutdown my laptop after mounting a CIFS share, dbus / network-manager is stopped before the shares from CIFS are unmounted. The shutdown process is paused at the unmount step until every timeout (one per share I think) is elapsed, causing my shutdown process sometimes to be longer than 2-3 minutes (remember laptop...).
I know the usual workarounds... diminish the CIFS umount timeout... remove dbus from the rc.X shutdown init scripts... make a logoff script that umounts for me... Stop using network-manager is not an option, I need it to configure my wireless connections.
Still, this issue is real, and is reproducible under every version of Ubuntu using network-manager I can remember of (edgy, gutsy, hardy, maybe not dapper), and the problem looks like a design flaw.
I can confirm that this is a problem on the AMD 64bit version of kubuntu 8.04.