Updating NIS clients through NFS

[Christiane Coda]

Hi,

I would like to know if it is possible to export the file systems which contain NIS maps to clients via NFS. That way, instead of having to do a "yppush" to update the clients, the clients would be automatically updated when files on the master are updated.

Is this supported? Does it work? OS = hp-ux 11.X

[harry d brown jr]

Why not just make your clients slaves?

live free or die
harry

[A. Clay Stephenson]

What has yppush ever done to hurt you? I can see several big problems with this: 1) Typically those maps are in the root filesystem; that's not one I would like to export to anybody. 2) If your NIS master goes down, you are really down because all your data is on one server.

I would not try this 'improvement'; I can't really see that it has any merits. Normally the overhead associated tith the yppush'es is very low and latency is not a problem.

[S.K. Chan]

I have not seen a NIS environment being implemented this way. The whole idea of NIS is to get away from having to mount a common "shared" system file to the clients. So to answer you question ..
>> Is this supported ? Does it work ?
I don't know.
Even if it does work, I would not run a NIS domain in such manner.

[Christiane Coda]

Hi,

Thank you for your answers. The reason for updating via NFS instead of through yppush is because we want the updates to happen automatically. Apparently, the updates don't have for a long period of time when the maps are updated. Is this period of time configurable? For instance, when maps are updated, how long does it take for the slaves to be updated as well? Can this be achieved "almost" instantaneously?

Thanks,

CC

[A. Clay Stephenson · Accepted solution]

Hi:

If you make the changes on the NIS master server and then do an explicit ypmake, the changes should be pushed out within seconds and certainly within a few tens of seconds.

If this is not happening, then you have an NIS problem probably with incorrect timestamps.

[S.K. Chan]

The timeout for each slaves is 30 sec and this cannot be changed. If you feel it's taking too long to timeout, you would have to identify which slaves not responding. Check for possible error log. You can even consider rebuilding the NIS database on the slave.