NIS Problem

[Anitha_3]

Hi,

i have a small query?? if i restart the NIS server do i need to restart the NIS Clients???

thanks in advance.
Govind.

[Bharat Katkar]

NO, Not required.
Regards,

[Anitha_3]

hi Bharat,

thank you, but after rebooting my NIS server the nis users are not able to workon.. any inputs for this.

[Sunil Sharma_1]

Hi Govind,

Please chack NIS serevr daemons(named)are running in NIS server.

Sunil

[john kingsley]

How did you originally setup NIS? Through SAM or command line?
Check the /etc/rc.config.d/namesvrs file on your NIS Master & Slave servers and make sure it is configured to start NIS during a reboot.

[Dave Olker]

Hi Govind,

If you're referring to the NIS client processes on the same system as the server, then I'd say yes - you should restart them, since the client processes on the server are usually bound to the server.

My rule of thumb for NIS processes on the same system are:

1. Always start the server before starting the client, so that the client has something to bind to.

2. Always stop the client before stopping the server so that the client will not be trying to bind somewhere that won't answer.

Normally, you'd have multiple NIS servers on a subnet, so stopping one server shouldn't affect other clients, but for the client services on the NIS server itself, they'll usually hang if you don't stop them first.

You can also use the "NIS Server List" function of NIS to specify a list of NIS servers to bind to in priority order, so that if one server goes away the clients will know exactly where to go to get to other servers.

So, for remote NIS clients, you shouldn't have to stop them provided other servers are available and the clients know how to get to them. For NIS client processes on the NIS server itself, I usually stop them first before shutting down the server just to save myself the hassle.

Regards,

Dave