[Bug 211631] Re: Network is brought down before network filesystems are unmounted (CIFS timeout at shutdown)
I have two machines running 11.04 with a wireless connection. I was able to get a clean shutdown on both by changing the link to /etc/init.d/umountnfs.sh in /etc/rc0.d and /etc/rc6.d from S31umountnfs.sh to K15umountnfs.sh. This is a workaround, not a fix, as it simply starts the cifs/nfs file unmounting script earlier in the shutdown process. -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to samba in Ubuntu. https://bugs.launchpad.net/bugs/211631 Title: Network is brought down before network filesystems are unmounted (CIFS timeout at shutdown) To manage notifications about this bug go to: https://bugs.launchpad.net/network-manager/+bug/211631/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 211631] Re: Network is brought down before network filesystems are unmounted (CIFS timeout at shutdown)
On a functional level perhaps it is worth considering whether Network Manager, on stopping, should simply leave the interfaces as currently configured instead of taking them down. I can make the argument that Network Manager is a tool to make it easy for the user to control network interfaces, but Network Manager is not the owner of those interfaces, the system and user are. If the user makes a connection using Network Manger and then disables NM, why shouldn't the interface stay up until the user or a shutdown sequence takes it down? -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to samba in Ubuntu. https://bugs.launchpad.net/bugs/211631 Title: Network is brought down before network filesystems are unmounted (CIFS timeout at shutdown) -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 211631] Re: Network is brought down before network filesystems are unmounted (CIFS timeout at shutdown)
Excerpt from Clint Byrum's comment #146 Excerpts from Mike Perrin's message of Mon May 23 20:28:52 UTC 2011: On a functional level perhaps it is worth considering whether Network Manager, on stopping, should simply leave the interfaces as currently configured instead of taking them down. I can make the argument that Network Manager is a tool to make it easy for the user to control network interfaces, but Network Manager is not the owner of those interfaces, the system and user are. If the user makes a connection using Network Manger and then disables NM, why shouldn't the interface stay up until the user or a shutdown sequence takes it down? Mike thats a great point and I think would be a design change for NM. It might then be best to bring that up with the upstream developers. As it stands now, NM does in fact own a network interface that it is set to manage, and so, we must architect the system around that. Bug (enhancement request) https://bugzilla.gnome.org/show_bug.cgi?id=650925 submitted 2011-05-24 01:05:57 UTC ** Bug watch added: GNOME Bug Tracker #650925 https://bugzilla.gnome.org/show_bug.cgi?id=650925 -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to samba in Ubuntu. https://bugs.launchpad.net/bugs/211631 Title: Network is brought down before network filesystems are unmounted (CIFS timeout at shutdown) -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 208531] Re: Samba update breaks nautilus network browsing
Steve, Thanks, your suggestion fixed my problem connecting to the private share, although the correct syntax is client lanman auth = yes. The bizarre behavior I reported when connecting through the network browser to the public share SD_MMC_c still exists, however. I probably should have Read The Fine Man page for smb.conf before posting, but grepping for lanman in smb.conf on both 8.04 beta and Fedora 8 produced no result and I gave up prematurely. May I suggest that the smb.conf file in the final version of 8.04 should at least contain the appropriate line, commented out, with explanatory notation such as: # Older servers may not support the higher level of default security for # password negotiation and may require uncommenting the following line. ; client lanman auth = yes Adding those lines to smb.conf is not very helpful for live CD boot, however, since the command line would need to be uncommented each time it is started, presuming no persistence. And if the default were changed for live CD boot only, it would fail after installation. This may be a case of shooting ourselves in the foot. We want people to try Ubuntu, but when they do they may not be able to connect to existing Windows or samba shares. Their response is likely to be doesn't work, I don't want to deal with it. This seems a classic example of technical correctness overcoming intelligent marketing. Mike -- Samba update breaks nautilus network browsing https://bugs.launchpad.net/bugs/208531 You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to samba in ubuntu. -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
