On Aug 10, 2004, at 5:57 AM, Jeremy Kitchen wrote:
Mitch (WebCob) wrote:Just a few ideas...
hey, brainstorming is good, it's just the ideas aren't always ;)
Another stupid idea...how about a mechanism where clam can have updates "pushed" to it, so servers controlled by the clam team can distribute mini updates to them. The admins would have to subscribe to it, like a listserv, only instead of through email, it's done through this theoretical mechanism. There wouldn't be traffic spikes (as big) for times where there *aren't* updated db's available, only when there are updates, and the updates are sent out as the clam servers are able to handle the load.
Maybe like a modified GPG-signed listserv system only on it's own "clam update daemon" port...take a little more configuration since the people installing clam would have to subscribe and install a GPG key or something like that in the process, but that shouldn't be something back-breaking to figure out.
Maintenance would have to be done for the subscription mechanism, etc., like a listserv would, but it may be something that could be done. May even be extendable so that a master server for a network could receive the updates from the clam site (pushed from clamserv) then in turn be told to push them out to machines on the internal network. (I know this could already be set up, but it may be easier through this type of model to set up and maintain...)
I'm probably overlooking something obvious, but again...just an idea, right? :-)
-Bart
------------------------------------------------------- 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
