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

[fil]

Johan, unless you use NIS on an laptop I recommend to deinstall network-manager and use the old style /etc/interfaces configuration. At least this works for me. Don't have the respective machine at hand right now, so I'm not 100% sure if it is karmic already but I positively think so.

g., fil


----- "Johan Walles" <johan.walles at gmail.com> schrieb:

> Has anybody managed to work around this on Karmic?
> 
> I just upgraded to Karmic, and my previous workaround is no good any
> more, and I now have to (re)start NIS manually at each boot :-(.
> 
> Also, the top of the bug page says "This bug affects you and one
> other
> person".  Considering the amount of people subscribed to this that
> doesn't sound reasonable, please mark the top of the bug page if
> you're
> affected!
> 
> -- 
> NIS has problems starting before the network comes up
> https://bugs.launchpad.net/bugs/50430
> You received this bug notification because you are a direct
> subscriber
> of the bug.
> 
> Status in “autofs” package in Ubuntu: Confirmed
> Status in “network-manager” package in Ubuntu: New
> Status in “nis” package in Ubuntu: Confirmed
> 
> Bug description:
> Binary package hint: nis
> 
> in /etc/rcX.d there are the symlinks, but I can not log in with a nis
> User.
> If I manually start /etc/init.d/nis from console with a local Account,
> after that I can log in with an NIS-account on Console and GDM.
> 
> This Bug appears after Update to Kernel -25. May be NIS starts to
> early,  before the Network is running.
> 
> To unsubscribe from this bug, go to:
> https://bugs.launchpad.net/ubuntu/+source/autofs/+bug/50430/+subscribe

-- 
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.