[Bug 354588] Re: NIS fails to bind to YP server during boot

2009-05-05 Thread fil
*** This bug is a duplicate of bug 50430 *** https://bugs.launchpad.net/bugs/50430 ** This bug has been marked a duplicate of bug 50430 NIS has problems starting before the network comes up -- NIS fails to bind to YP server during boot https://bugs.launchpad.net/bugs/354588 You received t

[Bug 354588] Re: NIS fails to bind to YP server during boot

2009-05-01 Thread Russel Winder
Resetting the NIS start number to 60 means that boots are quick on Jaunty. Not sure if the binding problem is still there though -- GDM starts and wipes the display. -- NIS fails to bind to YP server during boot https://bugs.launchpad.net/bugs/354588 You received this bug notification because yo

[Bug 354588] Re: NIS fails to bind to YP server during boot

2009-05-01 Thread MarianoAbsatz
I'm still on intrepid (I never upgrade a working machine after a couple of weeks after release)... anyway, I'll try Alain solution in my machine on Monday (today is non-working day here and I don't have NIS at home)... I'll renumber my startup scripts again as they were originally and trye the --no

[Bug 354588] Re: NIS fails to bind to YP server during boot

2009-04-28 Thread Russel Winder
I just upgraded to Jaunty and the huge delays getting through the NIS connection attempts are back. I notice that NetworkManager is now numbered 50 in the startup sequence whilst NIS is 29. I shall experiment with setting NIS to 60. -- NIS fails to bind to YP server during boot https://bugs.lau

[Bug 354588] Re: NIS fails to bind to YP server during boot

2009-04-04 Thread MarianoAbsatz
Well... in fact, I don't think this is quite so... The problem is how much time does ypbind take to actually start up and bind to the nis server... My guess is that if this is run on the server itself it should be somehow quick and otherwise, it will depend on network condition and nis server res

[Bug 354588] Re: NIS fails to bind to YP server during boot

2009-04-04 Thread Russel Winder
I just noticed that actually the timeouts still happen but they happen very much more quickly. So this shift in start number doesn't actually solve the timeouts problem but because of the different state of the network adapter it doesn't give the delays and so the user gets a much faster boot up.

[Bug 354588] Re: NIS fails to bind to YP server during boot

2009-04-03 Thread MarianoAbsatz
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) :-) ** Attachment added: "Patch to nis_3.17-14ubuntu2 to change the startup order so it starts after NetworkManager, but before gdm" http://launchpadlibrarian.net/24766382/start_nis_