Date: Fri, 27 Mar 1998 17:52:41 -0600 (CST) From: John Kenagy <jktheowl@bga.com> To: Mark Castillo <markc@Relationships.com> Cc: freebsd-questions@FreeBSD.ORG Subject: Re: NIS Server, also a client? Message-ID: <Pine.BSF.3.95q.980327172906.11639A-100000@barnowl> In-Reply-To: <199803272018.MAA24965@friends.relationships.com>
next in thread | previous in thread | raw e-mail | index | archive | help
On Fri, 27 Mar 1998, Mark Castillo wrote: > Is there any reason why someone would enable NIS client on an NIS Server? > Yes. The server would then have access to all of the network's maps. This is if you are not using the servers own /etc/* files to build maps but are using alternate files in /var/yp/*. If you are using alternate files (like passwd.alternate, or whatever), you can use NIS to append the network file (passwd.alternate) to the server's passwd file by making the server a client. There are other concerns with the local passwd entries not being in the NIS maps. Mail delivery might get broken. The flip side is that if you have master and slave servers running, there exist possibilities that they could cross bind. You should take steps to prevent that - ypset can be used to force binding to a particular server. You must also be sure the source files on the server are very clean or the whole thing can crash. Been there, done that.;-) If you haven't, read Stern's "Managing NFS and NIS" from O'Reilly. He writes with a Sun viewpoint so be sure to read the man pages as well. John To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-questions" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?Pine.BSF.3.95q.980327172906.11639A-100000>