From owner-freebsd-current Sat Jan 15 21:26:12 2000 Delivered-To: freebsd-current@freebsd.org Received: from apollo.backplane.com (apollo.backplane.com [216.240.41.2]) by hub.freebsd.org (Postfix) with ESMTP id 2CF3A15229 for ; Sat, 15 Jan 2000 21:26:11 -0800 (PST) (envelope-from dillon@apollo.backplane.com) Received: (from dillon@localhost) by apollo.backplane.com (8.9.3/8.9.1) id VAA02919; Sat, 15 Jan 2000 21:26:08 -0800 (PST) (envelope-from dillon) Date: Sat, 15 Jan 2000 21:26:08 -0800 (PST) From: Matthew Dillon Message-Id: <200001160526.VAA02919@apollo.backplane.com> To: The Hermit Hacker Cc: Rod Taylor , freebsd-current@FreeBSD.ORG Subject: Re: Thoughts... References: Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG :> :> There are lots of ways of syncing up that do not require sending the :> entire image over the network every time. Syncing is something you could :> do with an NFS mount quite easily, combined with something like cpdup :> (see /usr/ports/sysutils/cpdup). : :we use rdist on our network to keep our production servers in sync...we :tend to avoid 'nfs traffic' as much as possible... : :Marc G. Fournier ICQ#7615664 IRC Nick: Scrappy I've never trusted rdist for exact mirroring. I remember trying to use it at BEST and it not getting everything right, though I can't remember exactly what it didn't get right... probably things like devices and hardlinks. I wound up taking the 'stat' hit and having the clients scan the disk hierarchy for changes, and making sure the NFS server could handle it. But you do not have to do things that way -- for example, the server could keep track of the changes itself and send a list to the client which the client then copies via NFS. -Matt Matthew Dillon To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message