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

Re: ICEs, libc6, yp



Tor Slettnes wrote:

> >>>>> "Adam" == Adam C Powell IV <hazelsct@mit.edu> writes:
>
>     Adam> Thank you.  Unfortunately, I'm using the official 2.2.10
>     Adam> kernel-image-2.2.10-netwinder package, version 19990716, and
>     Adam> I still get this problem.  NFS mounts are fine, and the NFS
>     Adam> clients and yp clients are the same netgroup on the server.
>     Adam> Everything is the latest potato, and I've done "cd /var/yp;
>     Adam> make" on the server countless times...
>
> Have you taken a look at /usr/doc/nis/nis.debian.howto.gz?

Yup.  That's why it is working for my Intel clients. :-)

> It goes through each step of setting up an NIS master, slave, and/or client:
>
>   - /etc/init.d/nis needs to be changed on the master

Done.

>   - /etc/defaultdomain needs to be created both on server and clients

Done.

>   - On the master, you need to run through "/usr/lib/yp/ypinit -m"

Done.  Just did it again for good measure.

>   - When you are done, restart NIS:
>         /etc/init.d/nis stop
>         /etc/init.d/nis start

Done on the master and the client (in that order).  Server messages:
Setting NIS domainname to: mit.edu
Starting NIS services: ypserv yppasswdd ypxfrd ypbind
Client messages:
Setting NIS domainname to: mit.edu
Starting NIS services: ypbind

Also, /etc/yp.conf has the correct ypserver on the master and client.  Still
doesn't work on the Netwinder- "YPBINDPROC_DOMAIN: Domain not bound".

> On the master, try 'ypwhich'.  You should see its own host name if everything
> is OK.  If that works, try 'ypwhich' from the clients as well.

This gives the correct server name on the master and the intel clients.  On the
Netwinder, it gives:
can't yp_bind: Reason: Domain not bound

Thanks very much for the debugging help!  Hopefully we'll get to the bottom of
this soon.  It's not mission-critical, as the Netwinder really isn't a
functioning desktop yet.  I hope it might expose a problem in the software, and
lead to a fix that helps some others.

I'm having a couple of X problems, but I'll start them in a new thread...

-Adam P.



Reply to: