Date: Sat, 15 Jan 2000 21:26:08 -0800 (PST) From: Matthew Dillon <dillon@apollo.backplane.com> To: The Hermit Hacker <scrappy@hub.org> Cc: Rod Taylor <rod@zort.on.ca>, freebsd-current@FreeBSD.ORG Subject: Re: Thoughts... Message-ID: <200001160526.VAA02919@apollo.backplane.com> References: <Pine.BSF.4.21.0001150228310.46499-100000@thelab.hub.org>
next in thread | previous in thread | raw e-mail | index | archive | help
:>
:> 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
<dillon@backplane.com>
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-current" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?200001160526.VAA02919>