Intrepid and Jaunty fail to start NIS correctly

[Russel Winder]

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?

[Russel Winder (russel)]

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?

[Russel Winder (russel)]

With Jaunty, reassigning NIS from start number 18 to start number 60 so that it happens after NetworkManager start (start number 50) removes the delay but it is not clear that is solves the problem; it is a workaround not a fix.

[David Tombs (dgtombs)]

Thank you for taking the time to report this bug and helping to make Ubuntu better. This particular bug has already been reported and is a duplicate of bug 50430, so it is being marked as such. Please look at the other bug report to see if there is any missing information that you can provide, or to see if there is a workaround for the bug. Additionally, any further discussion regarding the bug should occur in the other report. Please continue to report any other bugs you may find.