[Date Prev][Date Next]   [Thread Prev][Thread Next]   [Thread Index] [Date Index] [Author Index]

RE: Fedora 10 ypbind error


> -----Original Message-----
> From: fedora-list-bounces redhat com 
> [mailto:fedora-list-bounces redhat com] On Behalf Of Ralf W. 
> Grosse-Kunstleve
> Sent: Wednesday, December 10, 2008 11:33 AM
> To: Community assistance, encouragement,and advice for using Fedora.
> Subject: Re: Fedora 10 ypbind error
> > top of a google[ ypwhich: Can't communicate with ypbind ]
> > http://docs.sun.com/app/docs/doc/802-3884/6i7ogkaot?a=view
> >
> > I think you are at the "NIS Service Is Unavailable" stage 
> of the document...
> > try the following, even if `/etc/init.d/ypbind status` 
> returns a pid:
> > ps aux | grep ypbind
> >
> > `/etc/init.d/ypbind status` may be reading a file from /var 
> instead of checking for a physically running program.
> The ypbind process is running according to ps aux. Same 
> process number as reported by /etc/init.d/ypbind status.
> Does someone have a working Fedora 10 NIS client? -- Just to 
> know if it works for others.

I did finally get NIS working with autofs for my home directory.  It was
messy though, the system-config-network tool and
system-config-authentication UIs made a mess of the /etc files.
ifcfg-eth0 was laughable at some point.  I think it set my broadcast
address as my default gateway.  

The order I went through config may have been part of the problem:
turning off DHCP, turning off Network Manager and turning network back
on, modifying /etc/sysconfig/network, /etc/nsswitch.conf, etc. 

I guess I'm saying I did most of the config manually.  I plan to upgrade
another workstation and see if there is a more direct path to getting it
bound to NIS.  

[Date Prev][Date Next]   [Thread Prev][Thread Next]   [Thread Index] [Date Index] [Author Index]