SG and NIS

[Alex Lavrov.]

Hello,

I wanted to know are there any recommendations about using NIS in SG environment?

The issue is, that when the NIS server/slave that the SG node is binded to is going down, it takes some times until the client is binded to another server. We have A class network so the bind takes a long time (broadcast) and I think that SG can fail.

So, what are the guidelines about working with NIS in SG environment?

Alex.

[melvyn burnard]

Generally th erecommendation is to have ALL of the cluster addresses, including packages, in /etc/hosts and have the /etc/nsswitch.conf point to hosts first, and then DNS or NIS, whichever is your preference.
This then allows nodes to rejoin or start the cluster if the NIS or DNS servers are not available or responding.

[Alex Lavrov.]

Thanx. My bad I didn't say that I'm more intersted about the /etc/passwd files.

Hosts are managed with DNS and enyway all the nodes are declared localy.

Thanx

[Kevin Wright]

don't use broadcast, specify your NIS master and slaves with ypinit -c.

Also, why are you using a class A network that is not subnetted?

[A. Clay Stephenson]

It's no problem at all --- as long as you can live with the inherent insecurity of NIS. I ran MC/SG with NIS both with and without DNS for many years and never had a problem. The binding shouldn't be a problem as long as you make certain that you have at least one slave server on the subnet --- and 2 slaves would be even better. In that case, at least one server is going to respond in a timely manner. It is a little odd to run a Class A network without breaking it into subnets --- that's what routers are made to do.

[Alex Lavrov.]

Thanx for the suggestions!

Kevin - in HP there is no "-c" option.

Alex.