> Message: 1
> Date: Mon, 6 Feb 2006 14:59:00 -0400 (AST)
> From: "Marc G. Fournier" <scrappy@...>
> To: pyzor-users@...
> cc: ftobin@...
> Subject: Pyzor server(s) ...
> Hi ...
> Since pyzor is pretty much the only viable 'clearinghouse'
> still, with
> everyone else starting to limit who can make use of it, I'm wondering
> what it would take to improve Pyzor ...
> The big thing I've seen on the lists is the timeouts
> issue, and, from
> what I can tell, the problem is that its all running on a
> single server
> right now ...
> Unfortunately, python isn't my language, so doing any
> coding on that
> side I'll be useless for, but I've been looking at how clamav
> is dealing
> with the virus signature updates and am wondering if its
> somehow possible
> to apply what they are doing to pyzor itself ...
> Now, granted, I have no idea how large the pyzord.db file is/gets,
> so, of course, this becomes a very big limiting factor, but with
> the clamav
> folks, all they do is use rsync to pass around the database itself to
> 'slave servers' ...=20
> The idea is to have one master server (db.pyzor.org) that
> all reports
> are submitted to, and several slave servers (db.xy.pyzor.org)
> that handle
> the check requests ... where xy would be a country code ...
> right off the
> bat, I could easily provide a db.us.pyzor.org and
> db.pa.pyzor.org server
> The only thing that would (I think) have to change in the
> pyzor code
> itself is allow for a master vs slave scenario in the config
> files, so
> what when discover is done, they get set appropriately, but I
> can't think
> that that would be too hard ...
> Frank, about what size is the pyzord.db file? How small
> does it shrink
> if compressed?
> Just my two cents, and an offer of server/network resources ...
I could also offer, at least temporarily ressources. I have a server
that doesn't do much right now on a very stable cable connection.
> Marc G. Fournier Hub.Org Networking Services
> (http://www.hub.org) Email: scrappy@... Yahoo!: yscrappy
> ICQ: 7615664
> pyzor-users mailing list
> End of pyzor-users Digest