On Fri, 13 Aug 2004 22:34:43 +0200 Tomasz Kojm <[EMAIL PROTECTED]> wrote:
On Sat, 14 Aug 2004 08:02:51 +1200 Jason Haar <[EMAIL PROTECTED]> wrote:
DNS for serial numbers plus HTTP for actual data transfer still sounds
New version of freshclam will work in this way. Big thanks to all for
the interesting thread !
How about incremental updates? Can it possibly make way to next freshclam versions too?
Checking serial number (or version) via DNS will certainly reduce some traffic on the mirrors, but I'm not sure how much of the 91.53 GB (last month traffic here for *.cvd) will be reduced. Version checking (assuming most clients use the new freshclam) in my raw calculation uses 173840 (cvd hit) * 512 bytes = 85 MB. Not much.
If we can use incremental update, for each database update we'll be distributing small ammount of data (say ... 1 - 5 kB) instead of the 162kB daily.cvd (or more) that we have now.
If we distribute the incremental update via DNS (I still have a thing for DNS), ISPs will cache this too so mirror traffic will be much much much reduced.
I have a Linode with 25 GB monthly bandwidth on a fast datacenter, and I'll be happy to contribute half of it for clamav db mirror. But since mirror bandwidth requirement is SOOO high, I can't do that can I? I'm sure that with lower bandwidth requirement many people will be happy to pinch in.
Regards,
Fajar
------------------------------------------------------- SF.Net email is sponsored by Shop4tech.com-Lowest price on Blank Media 100pk Sonic DVD-R 4x for only $29 -100pk Sonic DVD+R for only $33 Save 50% off Retail on Ink & Toner - Free Shipping and Free Gift. http://www.shop4tech.com/z/Inkjet_Cartridges/9_108_r285 _______________________________________________ Clamav-users mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/clamav-users
