NIS fails to bind to YP server during boot
Bug #354588 reported by
Russel Winder
This bug report is a duplicate of:
Bug #50430: NIS has problems starting before the network comes up.
Edit
Remove
This bug affects 1 person
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
nis (Ubuntu) |
New
|
Undecided
|
Unassigned |
Bug Description
Binary package hint: nis
On Intrepid booting a system that is expecting to bind to a YP server always goes into a:
binding to YP server...
...
...
...
...
...
etc. which takes ages. By default the start number of NIS is 18. However the default start number of Network Manager is 28 and so it is not really surprising that NIS is failing to bind since there is no network connection yet.
By setting the NIS start number to 30, i.e. something greater than 28, the problem goes away and booting is significantly extremely much faster.
Perhaps the default NIS start number should be changed?
To post a comment you must log in.
OK... but GDM start number is 30 (and g < n), so I think that 29 is a better number than 30 (and is prime also) :-)