<br>
<div><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">2) Configure the mail server as an NIS slave. I'm thinking that this<br>will basically "copy" the user info (username, password, homedir,
<br>etc.) on a schedule and store it locally on the mail server (is this<br>how it works?). This covers both issues - power outage and a server<br>dying. But I've read about problems getting password sync to happen<br>quickly. I'd ideally like it to happen immediately (without any
<br>manual intervention) but I don't think this is possible.<br><br>Thoughts?<br><br>Jeff Graves, MCSA<br>Customer Support Engineer</blockquote><div><br>
<br>
I have not used NIS for quite some time, rdist and ssh keys are much better for this simple task.<br>
<br>
Home dir's in the Sun NIS model is handled via a NFS mount of the home dir from a common home dir server.<br>
<br>
In NIS all slaves can also be clients. Slaves get the passwd, group, shadow, and other<br>
maps from the master via a transfer which is started/controlled by the master. So, as soon as the master and slaves<br>
are up, the master will push out maps if they have been changed. If the master crashes the slaves should have the most current<br>
maps. <br>
<br>
NIS is a slow process in general, one twist is to config all slaves to be clients first, then slaves. Slaves configed this way<br>
will query the master (as a client) and if this fails query their local maps (as a slave). <br>
<br>
</div><br>
</div>James H. Edwards<br>Network Systems Administrator<br>Judicial Information Division<br><a href="mailto:jedwards@nmcourts.com">jedwards@nmcourts.com</a>