*** This bug is a duplicate of bug 50430 *** https://bugs.launchpad.net/bugs/50430
On Tue, 2009-10-13 at 18:16 +0000, Chuck Short wrote: > *** This bug is a duplicate of bug 50430 *** > https://bugs.launchpad.net/bugs/50430 > > ** This bug has been marked a duplicate of bug 50430 > NIS has problems starting before the network comes up Why has this bug been marked as a duplicate of 50430? 50430 talks about NIS (ypbind) not working properly on NetworkManager enabled systems. That should be fixed for a few releases now, and indeed I haven't seen it on my systems in a while. My suspicion is that the people who are still having trouble are really having problems with NetworkManager not detecting/reporting the network status of their systems properly (saying the network is up when it isn't or vice versa). This bug (213574) is about autofs not working properly on NetworkManager enabled systems. That is basically the same problem, but a completely different package (in fact that's my major complaint about NetworkManager: adding it to your system requires that you go around and hack on each network-aware service on your system, one at a time, to make them compatible with NetworkManager). I've not upgraded to Karmic but I've seen absolutely nothing that leads me to believe anyone has made any effort to enhance autofs, either the daemon itself (a la ypbind) or even just the init scripts, to be NM-aware. Until that happens this bug will not be fixed. What has to happen on a very abstract level is that you can't start autofs until all the services that it utilizes (based on /etc/nsswitch.conf for example) are running, if they are supposed to be started. It's hard because on many systems, /etc/nsswitch.conf lists "nis" or "nisplus" as a source for automount, and yet these services are not enabled. On other systems, automount data is taken from LDAP. Other places it comes from flat files. Etc. And remember, by "running" I don't just mean that the init script has completed. In the brave new world of NetworkManager, having the init script complete does NOT mean that the service is available. It just means that it may _become_ available, sometime later. autofs has to wait until these services are actually active, before it can start. In the old days, with a simple serialized boot process implying that once an init script was complete that service was available, this was simple. Now it's become very tricky indeed. -- Autofs fails to start with maps from NIS https://bugs.launchpad.net/bugs/213574 You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to autofs 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