Setting up NIS in a cluster
 

I am looking for assistance in setting up NIS in a Redhat Clustered environment. Before you give me any grief about using NIS, I know the arguments and am working on getting us to kerberos but I have NIS for now.

What is happening is that I have the scripts for ypbind, ypserv, yppasswdd, and ypxfrd and portmapper in an NIS service. When I fail the system over it says the service restarts but it appears that is not the case. I manually restart ypserv and ypbind and it seems to work OK till it fails back to the other node.

Anyone out there get this working correctly? I even tried adding the status to the startup scripts but it puts it into a restart loop.

I've not had much experience with clustering, but have used NIS alot.

It seems your basically making a NIS master server, but the server is clustered to avoid NIS outage?

If thats the case, why you use cluster at all? Why not just have NIS slaves dotted around your network which sync from the master and you have better coverage?

If you have to use the clustered approach, I'm assuming the NIS service is down on one side, and when one node falls over, this triggers the NIS restart script on the other node? Have you just tried an /etc/init.d/nis start as part of the cluster handover in place of a bespoke script?

Stuart.

Setting up NIS in a cluster
 

All,

I got it working this morning. In RHEL, it does not return the value when it runs a status. I added a RETVAL variable to ypserv, yppasswdd and ypxfrd and it seems to work great now!

Thanks!