Intrepid and Jaunty fail to start NIS correctly
Bug #303072 reported by
Russel Winder
This bug report is a duplicate of:
Bug #50430: NIS has problems starting before the network comes up.
Edit
Remove
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Ubuntu |
Confirmed
|
Undecided
|
Unassigned |
Bug Description
I beleive this is a long standing bug (Hardy, Feisty, Gutsy, . . ) but it still has not been fixed in Intrepid. Intrepid boots fine to the point at which it is trying to connect to the NIS server (which is running). After a while the attempt times out and the boot continues -- and at the end of which NIS works fine.
So why is it that the initial attempt to do a NIS connection is so slow and in the end fails?
Is this just a daemon start ordering problem?
To post a comment you must log in.
I just upgraded to Jaunty and the problem is there as well, NIS takes forever to start. Should the title of this bug be amended or should a new bug be opened?