From owner-freebsd-questions Sun Dec 30 9:35:47 2001 Delivered-To: freebsd-questions@freebsd.org Received: from serv1.wallnet.com (server1.wallnet.com [208.225.162.122]) by hub.freebsd.org (Postfix) with ESMTP id A5EC337B417 for ; Sun, 30 Dec 2001 09:35:35 -0800 (PST) Received: from localhost (timothyk@localhost) by serv1.wallnet.com (8.11.5/8.11.5) with ESMTP id fBUHZPN70566; Sun, 30 Dec 2001 12:35:26 -0500 (EST) (envelope-from timothyk@serv1.wallnet.com) Date: Sun, 30 Dec 2001 12:35:25 -0500 (EST) From: Tim Kellers To: Gabriel Ambuehl Cc: Bill Moran , Subject: Re[2]: "Cluster" administration software... In-Reply-To: <70187884814.20011230181729@buz.ch> Message-ID: <20011230122856.F70028-100000@serv1.wallnet.com> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-questions@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG I used rsync (and a ruleset) to "clone" an old box to a new box (both FreeBSD 4.4). I maintain exact copies of /etc/* and /usr/local/* on several other servers by croning rsync, too. Interestingly enough, while at first I did this on boxen that were identical hardware (Dell Poweredge 2500's), I subsequently rsynced folders on different hardware (Poweredge 1300, 1400, 1400SC, and an Optiplex, just for good measure) and I had zero erros or inconsistencies among these boxes. I also heavily use Webmin for the "little" stuff for maintaing our server forest. I does exactly what I need it to do. Tim Kellers CPE/NJIT On Sun, 30 Dec 2001, Gabriel Ambuehl wrote: > -----BEGIN PGP SIGNED MESSAGE----- > > Hello Bill, > > 30 Dec 2001, 18:08:17, you wrote: > > >> Last time I looked into NIS it was for stuff like keeping > >> /etc/passwd etc in sync, but not updating packages on hosts. > > No, I was suggesting it for the purpose of "globals configuration" > > which I had assumed would include passwd, groups, hosts. It > > appears I > > misunderstood. > > Well, maybe I wasn't concise enough. By global configuration I meant > stuff like rc.conf, resolv.conf etc pp, i.e. stuff that needs to be > changed to reflect local configuration but can be correct site wide. > > > Hmmm ... well, portupgrade is the best tool I know of currently, > > there's an interesting article by Michael Lucas that may give you > > some ideas on how to make it work better: > > http://www.onlamp.com/pub/a/bsd/2001/11/29/Big_Scary_Daemons.html > > but I don't know of anything better. > > Except for the docproj stuff which I don't need, I knew everything > pointed out there. > > >> run Debian at home and they told me that apt-get never did any bad > >> to their system... > > Sounds "too good to be true" but if it really works that well, it > > might be worth porting (if possible > > The short glance I had at apt reminded me heavily of the FreeBSD > ports > and AFAIK, .deb was modeled after them with some improvements. > > > I don't understand that from a server perspective. I mean, what > > happens if something automatically upgrades something that no > > longer works? I always want to be involved when upgrades are in the > > works. > > Well, I don't plan to run portupgrade --all from crontab, but > something like > portupgrade --everything-on=http://myrepository/packages > for sure would be nice, i.e. specifying a custom repository of > packages which are known to be working as you've built them yourself > on one of your test boxes and now you just need to distribute them > over your farm... > > >> I've been thinking about implementing some SOAP based small > >> server, that takes the package and calls portupgrade on it... > > That would probably be a useful project, something like an enhanced > > portupgrade program that worked across the network via ssh or > > something. I don't know of anything that does it right now. > > Well, rdist and not so bad distribution both try to solve the same > task but both don't seem to know anything about FreeBSD ports and > thus > aren't of much value here... > > >> Cluster User administration for sure looks cool but I don't really > >> need to keep passwd in sync (actually, this would probably be > >> counter productive from a security point of view with our system). > > Doesn't sound like NIS will work for you then. > > > ACK. > > > > Best regards, > Gabriel > > -----BEGIN PGP SIGNATURE----- > Version: PGP 6.5i > > iQEVAwUBPC8+HMZa2WpymlDxAQFyZQgAn+C9Zsq7zJYzzPSWlUyHt1R7MdmBXPon > 7ezlHhpuDNk3iLwelB+82wUDqDAFcOIhwP3F3cVB1yfNGDpjp82vqIEVudmr12D/ > LVrC/yRBIkxCu373O2RefKePaE5To3ErBRL6MmvRAfFkIvTcfGEQFESR/gJZTB8t > 8G1qOSWUlhqrl2Mi8FPrONoLVOZ0YKGuTyXPldYP3pNJ6kRDSdbztGAXalmQAoGP > fg5RbjNoKiQObLum40VExaTZKLSGd6NT1rI/czJN1nndsCpLK8xexqNvSvw/DKAb > y7du5BOnKKtz5jOOg/bTVWF/9RojgVBjGjkarFnyw8sYGcigXgxOMA== > =wiNb > -----END PGP SIGNATURE----- > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-questions" in the body of the message > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-questions" in the body of the message