This appears related to bug #50430. It makes booting take forever because NIS is trying to bind to the domain and can't find the network, which then appears to break lots of other stuff (HAL, networking, etc.) I am seeing this behavior with the Intrepid Ibex beta and remember seeing this kind of behavior with the Gutsy beta also. The problem as I see it is that nis, and autofs, have a priority in the init process before Network Manager, thus they start before the network is totally configured. The way I fixed the issue on my system was to go into the /etc/rcX.d directories and change the hard links so that NIS and autofs start after Network Manager. (Thus S18nis becomes S31nis and S19autofs becomes S32autofs). This fixed all of the issues I had with NIS and autofs. It seems much simpler than some of the other suggestions such as completely removing Network Manager, etc.
-- When nis server is not reachable during startup, system gets very slow and HAL fails to initialise https://bugs.launchpad.net/bugs/252499 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list [email protected] https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
