From owner-freebsd-hackers Wed Jun 25 04:15:14 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id EAA17145 for hackers-outgoing; Wed, 25 Jun 1997 04:15:14 -0700 (PDT) Received: from cais.cais.com (root@cais.com [199.0.216.4]) by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id EAA17140 for ; Wed, 25 Jun 1997 04:15:11 -0700 (PDT) Received: from earth.mat.net (root@earth.mat.net [205.252.122.1]) by cais.cais.com (8.8.5/) with SMTP id HAA28047; Wed, 25 Jun 1997 07:15:09 -0400 (EDT) Received: from Journey2.mat.net (journey2.mat.net [205.252.122.116]) by earth.mat.net (8.6.12/8.6.12) with SMTP id HAA14796; Wed, 25 Jun 1997 07:15:07 -0400 Date: Wed, 25 Jun 1997 07:14:42 -0400 (EDT) From: Chuck Robey X-Sender: chuckr@Journey2.mat.net To: John-Mark Gurney cc: FreeBSD-Hackers Subject: Re: NIS In-Reply-To: <19970625010619.04305@hydrogen.nike.efn.org> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk On Wed, 25 Jun 1997, John-Mark Gurney wrote: > Chuck Robey scribbled this message on Jun 24: > > I have been reading about NIS, trying to come to grips with it all, but I > > haven't been able to com eup with an answer to one last stumbling block. > > Maybe someone here knows what I don't ... > > > > I'm trying to figure out a flexible and reliable setup for a small ISP > > that has maybe 5 machines. What I would ideally like is to have a main > > server, have the database on that server duplicated on a second machine > > just in case the first machine has to go down for maintenance (or some > > catastrophe), and the rest of the machines be slaves. I'm particularly > > interested in the passwd map. > > actually.. FreeBSD's NIS implementation is quite secure... as long as > you know your wires are secure there shouldn't be any problems... John-Mark, you've misunderstood me somewhat. I'm not concerned with security from a hackers viewpoint (yet), I'm worried about having the master server go down. I want a fallback to aonther server, with only a little loss, even from a booting perspective ... I mean, if a slave master can't find a main master on boot, it needs to have a fallback that is at least reasonably up to date. I know exactly how the map files get built _and_ get updated. I'm not concerned with the db files, I'm worried about the method that the slave server would use if it couldn't find the master, when it boots. I'm willing to lose the last few hours of passwd activity, so what happens in that case? ----------------------------+----------------------------------------------- Chuck Robey | Interests include any kind of voice or data chuckr@eng.umd.edu | communications topic, C programming, and Unix. 213 Lakeside Drive Apt T-1 | Greenbelt, MD 20770 | I run Journey2 and picnic, both FreeBSD (301) 220-2114 | version 3.0 current -- and great FUN! ----------------------------+-----------------------------------------------