> > NIS Master in US. > > NIS Slaves scattered about the world. > > (No LDAP.) > > (No AD, although it might be a possibility) > > > > WAN goes down, nobody cares. (Well, all the systems stay up and > usable.) > > No separation of which-password-where. > > Create a user here, it appears everywhere. > > ? > > For the two last points, I am assuming that's only true in the UNIX > environment, if your users use MS Windows systems, they have different > passwords there (or have to keep them in sync manually themselves) ? > > Right ?
Correct you are. I could have worded it more clearly from the start. I meant to say: I don't have separate NIS domains just because there are separate offices in different countries. Let there be a NIS master somewhere, and each of the other offices has a slave or two. Perhaps the master could even be AD, in which case, you really could have unified AD/Linux passwords, create the user once, and it's always in sync everywhere. I have used AD NIS before, but only on a single server. Never did any sort of NIS replication that way before. I'm venturing a guess that it would be a pretty good solution, if you are ok with the limitations of the MS version of NIS. _______________________________________________ Tech mailing list [email protected] http://lopsa.org/cgi-bin/mailman/listinfo/tech This list provided by the League of Professional System Administrators http://lopsa.org/
