Comment 36 for bug 50430
Revision history for this message
| Desert Penguin (jtbock-daylight) wrote | #36 |
© 2004
Canonical Ltd.
•
Terms of use
•
Data privacy
•
Contact Launchpad Support
•
Blog
•
Careers
•
System status
•
67d34a1
(Get the code!)
My problem system: Dell Dimension E521, 2GB ram, AMD 64x2 5000+
I had this problem (nis failed to start, which cascaded to autofs not being able to read the yp auto.home map) in 8.04, but just worked around by restarting nis and autofs after system was up.
I upgraded (via a complete reinstallation) to 9.04 (amd64) earlier this week. The nis problem is now much more severe, at least for me. If nis is enabled, the system will take a very long time to boot and (possibly) never fully come up. The first problem is the same nis issue...starting nis fails. After trying to ypbind 10 times, the boot process then hangs a couple of lines later when it reaches hald. It stays at hald for a long time (10 minutes?). After making it past that, things seem to proceed normally until it tries to switch back to graphics and display the login screen. The mouse is visible (but not movable) on a whitish background. Maybe it would eventually come up, but I've never waited longer than 15 minutes or so.
One can ctl-alt-f2 and login with a local account, which takes a couple of minutes. Moving around via the command line seems mostly ok, but "sudo" anything, and you are going to be waiting minutes for the password prompt. And the gui, back on f7, never seems to change from its whitish background.
Starting nis once the system is up is fine, but the trick is actually getting the system to usable state.
So now, reboots are somewhat more complicated, as I have to disable nis, reboot, and then enable and start nis once the system is up. I haven't tried moving nis (and thus autofs) to later in the boot sequence to see if that would help.