[Bug 50430] Re: NIS has problems starting before the network comes up

[Russel Winder]

The workaround for this is well known but is not really explained
anywhere in any one place; there are comments on all the bugs related to
this one (especially 354588) and also in the Ubuntu forums.  What is
comes down to is the ordering of startup of NIS and NetworkManager.  If
NetworkManager is allowed to start after NIS then NIS takes ages to time
out hence the boot delay.  If NIS is started after NetworkManager then
NIS still fails to start properly at this time but its time outs are
much quicker and so there is no noticeable delay in booting.  NIS
binding still completes correctly once NetworkManager completes its boot
up later in the cycle.

So the workaround had to rearrange the boot order.  In particular to
reset the start number of NIS to 60 -- something sufficiently after 50
(the start number of NetworkManager) that things work.  So if you use
the services manager tool:

    System | Administration | Services

You unlock the settings then check the properties of NIS and reset the
start number for all active run levels to something bigger than
NetworkManager.  In my case I chose 60.

I have no idea how the changes is boot system coming with Karmic will
affect all this.  Given that the problem has existed for years and
whilst confirmed no real fix has been made, I fully expect the upgrade
from Jaunty to Karmic to result in total chaos requiring manual fixing
by the user -- again.

OK so I am grumpy, but this problem has been known for over 3 years and
not been properly addressed by the Ubuntu team.

Let us hope my fears do not come to fruition.

-- 
NIS has problems starting before the network comes up
https://bugs.launchpad.net/bugs/50430
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to autofs in ubuntu.