I've just installed RH7.2 on several different laptops. The only laptop 
behaving strangely is my own. Ypbind fails every time the machine starts. It 
binds to our domain, but fails when listening for a NIS(?)-server. Then it 
hangs almost forever on netfs, but the machine finally mounts my NFS-disk. 

Most of the times, ypwhich reports the server as it should, even if it 
claims that it failed at boot. If I do "/etc/init.d/ypbind restart" after 
I've logged in, it works like it should.  The strange thing, at least for me, 
happens if I let netfs start up before ypbind. netfs fails, but ypbind now 
works like it should. But then I have to run  "/etc/init.d/netfs start" after 
I've logged in.

My laptop uses a pcmcia card. I've tried changing the startup sequence of the 
different daemons, but nothing helps. All the other laptops have a built in 
ethernet card. These other laptops binds to the domain at boot, finds the 
NIS-server at once and mounts NFS-disks with no delay.  The configuration 
files are exactly the same on all the machines.

I suspect I've missed something obvious, but anyhow: Does anybody have a 
suggestion on how to fix this? 

-- 
Øystein Olsen, [EMAIL PROTECTED], http://folk.uio.no/oeysteio
Institute of Theoretical Astrophysics, http://www.astro.uio.no
University of Oslo, Norway



_______________________________________________
Redhat-list mailing list
[EMAIL PROTECTED]
https://listman.redhat.com/mailman/listinfo/redhat-list

Reply via email to