NIS binding

[Steve_3]

Help:

I have a client machine that gets unbind from the NIS server. How can I set it to automatically rebind to the NIS server.

Thanks,

Steve

[Antoanetta Naghiu]

ypbind -s.
You can edit as well /etc/rc.config.d/namesvrs.

[Rick Garland]

I would think you have problems elsewhere if the NIS client unbinds from a NIS master server or NIS slave server(s). Do you have a lot of network traffic? Is the NIS server going down periodically? The NIS client should bind to another NIS server if a server becomes unavailable. It goes and looks which server gives the fastest response (other variables such as proximity play a role as well). If you only have one NIS server, I would look into the feasibility of creating another NIS slave server.

[Anthony deRito]

Steve, you can use the command:

rpcinfo -b 100004 2

to make a RPC broadcast from your client that loses its binding to the server. (Use rpcinfo -p | grep ypserv on your NIS server to determine correct version.) You should be returned the IP and hostname of your NIS server running ypserv. If you do not, the service is unavailable. When a client binds to a server, it will use rpc calls like this to look for ANY server on your network running the ypserv daemon.

You should have a backup NIS server somewhere else on your network in the event that this service is unavailable. RPC calls will find this server if it exists.

Use ypinit -s to create the NIS slave server.

If the primary is unavailable for whatever reason, the NIS client will automatically bind to the slave NIS server.

In the event the master server comes available again, the client may bind to that server.

Setting up a backup server is fairly easy. ypinit -s will copy the databases from the master server. Your ypservers map will be updated with the new slave server.


Tony

[Steve_3]

I think I will set up the NIS slave server. Thanks for your input.

Steve