This is still the case on 11.10 - for some reasons, autofs sometimes starts before the network connection has been fully established. In those cases, I can see it complain in syslog about "hostname lookup failed: Name or service not known", so apparently, it failed to resolve the host name it's supposed to mount the shares from. This does not happen every time - looks like some sort of race condition.
-- You received this bug notification because you are a member of Desktop Packages, which is subscribed to network-manager in Ubuntu. https://bugs.launchpad.net/bugs/482236 Title: network manager breaks autofs Status in “network-manager” package in Ubuntu: Confirmed Bug description: Binary package hint: network-manager Ubuntu 9.10 network-manager Network manager tends to break autofs remote mounting of home directories. I believe what is happening is that autofs in being started before network manager has a working network connection and then it just fails. I can get autofs to work by logging in a user with a local home directory and restarting autofs after boot is finished. In 9.04 I was able to fix the problem by reordering init scripts mv /etc/rc2.d/S50NetworkManager /etc/rc2.d/S26NetworkManager mv /etc/rc2.d/S18nis /etc/rc2.d/S27nis mv /etc/rc2.d/S19autofs /etc/rc2.d/S28autofs and adding sleep 20 to /etc/init.d/NetworkManager right before it exits. However it appears 9.10 has moved more thoroughly to upstart so I could not easily implement this fix. I currently have things working fine by simply uninstalling network manager (since I don't need it on a desktop), but it is unfortunate that the default breaks like this. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/482236/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : [email protected] Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
