ypbind running on MDs but not core is this intentional?

[phenigma]

I'm trying to determine the home directory for a user on a hybrid and MDs using NIS.  ypmatch works great on MDs but ypbind doesn't appear to be running on the core causing ypmatch queries to fail when executed form the core.

Is ypbind running on the core for anyone else?

If not...
Does anyone know if ypbind is disabled on the core for a specific reason?

Thanks in advance.

J.

[tschak909]

yes, study how NIS works.

NIS is all about replication of system configuration files.

ypbind provides replication services for NIS slave servers. Not NIS master servers, as in the case of the core.

-Thom

[phenigma]

Thanks Thom!

I've been reading, but I'm off to do more!

I was originally under the impression that I would have to use ypmatch to grab data from NIS.  But, it looks like NIS takes care of replicating the information across multiple machines, and that it can be then accessed locally at each system using 'getent'.  At least that is my understanding right now.  You're statement about the replication of system configuration files pretty much says it all.  I am going to do some more reading though.  Thanks again for the push in the right direction!

J.