Date: Fri, 13 Jun 2003 11:41:01 -0700 From: Marcel Moolenaar <marcel@dhcp01.pn.xcllnt.net> To: Ken Smith <kensmith@cse.Buffalo.EDU> Cc: freebsd-hubs@freebsd.org Subject: Re: RFC - extra sync functionality... Message-ID: <20030613184101.GA585@dhcp01.pn.xcllnt.net> In-Reply-To: <20030613141421.GD13868@electra.cse.Buffalo.EDU> References: <20030613141421.GD13868@electra.cse.Buffalo.EDU>
next in thread | previous in thread | raw e-mail | index | archive | help
On Fri, Jun 13, 2003 at 10:14:21AM -0400, Ken Smith wrote: > > We would probably recommend (or implement in this some sort of force > mechanism...) running a real transfer pass once a week or so "just > because" in case someone(s) don't quite play nice with the serial > number generation and update content by mistake. If the transfers are more costly than ftp-master doing some checkums, you can also check if zones are changed without having a new serial number by attaching a md5 checkum to the zone. The checksum can be create with something like: ZONEMD5=`tar cf - $ZONEDIR | md5` You can validate checksums with a cron job and we can even bump the serial automaticly if the checksums don't match (provided there was a serial). > Is this a good idea? Is it worth seeing if existing practice on ftp-master > can be changed? By all means. I think the biggest win is having some synchronisation between someone doing an upload and the "system" doing the mirroring. -- Marcel Moolenaar USPA: A-39004 marcel@xcllnt.net
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20030613184101.GA585>