From owner-freebsd-questions Thu Feb 10 11: 5:18 2000 Delivered-To: freebsd-questions@freebsd.org Received: from benge.graphics.cornell.edu (benge.graphics.cornell.edu [128.84.247.43]) by builder.freebsd.org (Postfix) with ESMTP id 3F49A4543; Thu, 10 Feb 2000 11:05:12 -0800 (PST) Received: from benge.graphics.cornell.edu (mkc@localhost) by benge.graphics.cornell.edu (8.9.3/8.9.3) with ESMTP id OAA34165; Thu, 10 Feb 2000 14:04:46 -0500 (EST) (envelope-from mkc@benge.graphics.cornell.edu) Message-Id: <200002101904.OAA34165@benge.graphics.cornell.edu> To: Bill Swingle Cc: "[gill]" , unfurl@FreeBSD.ORG, questions@FreeBSD.ORG Subject: Re: NIS: Handbook sec. 15.5.3.2.2. In-Reply-To: Message from Bill Swingle of "Thu, 10 Feb 2000 10:20:58 PST." <20000210102058.A12561@dub.net> Date: Thu, 10 Feb 2000 14:04:46 -0500 From: Mitch Collinsworth Sender: owner-freebsd-questions@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG >Normally the yp slave server will do their best to keep synced with the >masters but this is not guranteed to always happen. If you have a >network with a lot of traffic these attempts at syncing might fail. This explanation is really a bit backwards. What really happens is when changes are made on the master server it runs yppush which sends a "map transfer" request to each slave server. When/if a slave server receives this request it runs ypxfr and pulls the new copy of the map from the master. There is really no best effort thing happening on the slave server "normally". The cron jobs are to clean up anywhere that yppush fails. >The >entries in crontab make sure that at least the most important maps get >updated specificly. Yeah, that, or whatever else you decide to do with them. Mine look like this: 23 * * * * root /usr/local/scripts/ypxfr_1perhour 24 01,13 * * * root /usr/local/scripts/ypxfr_2perday 25 01 * * * root /usr/local/scripts/ypxfr_1perday The referenced scripts: % cat /usr/local/scripts/ypxfr* # ypxfr_1perday - Do daily Network Information Service map check/updates /usr/libexec/ypxfr group.bygid /usr/libexec/ypxfr group.byname /usr/libexec/ypxfr networks.byaddr /usr/libexec/ypxfr networks.byname /usr/libexec/ypxfr protocols.byname /usr/libexec/ypxfr protocols.bynumber /usr/libexec/ypxfr rpc.byname /usr/libexec/ypxfr rpc.bynumber /usr/libexec/ypxfr services.byname /usr/libexec/ypxfr ypservers # ypxfr_1perhour - Do hourly Network Information Service map check/updates /usr/libexec/ypxfr master.passwd.byname /usr/libexec/ypxfr master.passwd.byuid /usr/libexec/ypxfr passwd.byname /usr/libexec/ypxfr passwd.byuid # ypxfr_2perday - Do twice-daily Network Information Service map check/updates /usr/libexec/ypxfr hosts.byaddr /usr/libexec/ypxfr hosts.byname /usr/libexec/ypxfr mail.aliases /usr/libexec/ypxfr netid.byname /usr/libexec/ypxfr netgroup /usr/libexec/ypxfr netgroup.byhost /usr/libexec/ypxfr netgroup.byuser This is the framework inherited/collected from NIS running on a variety of platforms over the last 10 years. -Mitch To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-questions" in the body of the message