From owner-freebsd-questions Mon Mar 9 20:07:34 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id UAA00313 for freebsd-questions-outgoing; Mon, 9 Mar 1998 20:07:34 -0800 (PST) (envelope-from owner-freebsd-questions@FreeBSD.ORG) Received: from Kitten.mcs.com (Kitten.mcs.com [192.160.127.90]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id UAA00260 for ; Mon, 9 Mar 1998 20:07:17 -0800 (PST) (envelope-from font@Jupiter.Mcs.Net) Received: from Jupiter.Mcs.Net (font@Jupiter.mcs.net [192.160.127.88]) by Kitten.mcs.com (8.8.7/8.8.2) with ESMTP id WAA10641; Mon, 9 Mar 1998 22:07:15 -0600 (CST) Received: from localhost (font@localhost) by Jupiter.Mcs.Net (8.8.7/8.8.2) with SMTP id WAA18903; Mon, 9 Mar 1998 22:07:14 -0600 (CST) Date: Mon, 9 Mar 1998 22:07:14 -0600 (CST) From: Font To: Doug White cc: Atipa , questions@FreeBSD.ORG Subject: Re: How to setup NIS slave server? In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-questions@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I have done this once before, but lost Atipa's original post. Through Doug White's magic, though, I can make a decent reply. A slave server is started up by configuring the rc.conf pretty much as one configures the master server. However, the maps on the slave must be manually transferred over the first time the slave is set up. I use a script something like this (soft returns where appropriate): #!/bin/sh for i in group.bygid netid.byname protocols.bynumber group.byname networks.byaddr rpc.byname hosts.byaddr networks.byname rpc.bynumber hosts.byname passwd.byname services.byname master.passwd.byname passwd.byuid ypservers master.passwd.byuid protocols.byname do echo $i /usr/libexec/ypxfr -d mydomain -h mymaster.dom.com -s mydomain $i done This is run on the slave. Of course, on the master, the ypservers file in /var/yp should know about the slave server. Generally, you need an NIS server on each network. Since NIS clients bind using broadcasts, they won't cross networks. Generally a slave server also has itself as a client. Credit for all of my words really goes to Bill Paul, who sent me an informative message when I was starting out with NIS. Now I return the favor to everyone else. :-) A bug in my MUA causes news.announce.newusers font to be sent to beneficiaries and senders of UCE/SPAM. @ mcs.net Wishes are like dishes. On Mon, 9 Mar 1998, Doug White wrote: > Date: Mon, 9 Mar 1998 00:24:35 -0800 (PST) > From: Doug White > Reply-To: Doug White > To: Atipa > Cc: Robert Beer , stephen farrell , > freebsd-questions@FreeBSD.ORG > Subject: Re: How to setup NIS slave server? > > On Sat, 7 Mar 1998, Atipa wrote: > > > > > Thanks to all who helped w/ my earlier quesiton. Got everything working > > fine. > > > > NIS is doing everything I want it to, except maintain multiple servers. I > > can not find any documentation anywhere as to how one would designate > > master/slave servers. ypserv has no such option. > > Although I don't claim to be a NIS expert, I'm under the impression that > `slave' servers are defined by the client using ypset -S. Slaves can act > like DNS secondaries and ypbind to the master server to grab data, though. > > I'm hoping you found the yp and ypserv man pages by now. > > Doug White | University of Oregon > Internet: dwhite@resnet.uoregon.edu | Residence Networking Assistant > http://gladstone.uoregon.edu/~dwhite | Computer Science Major To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-questions" in the body of the message