> Noone has suggested "maximum". The issue is that the mirrors are so > overloaded that it's often taking freshclam an excessive amount of > time to do its thing, because of the time-outs / connection > failures. No big deal if it's the update run in the background. But > if it's on-demand update preceding a user-driven scan, it's making > the user sit there, twiddling its thumbs, for up to a minute or two.
Are we really having this protracted discussion, because we don't want someone to have to sit for "up to a minute or two"? This problem seems overstated. I mean, are we talking about on-demand scans perhaps a dozen or more times per day, every day? i.e. is this adding up to hours of lost time every week? If so, is it really such a problem to have a database that is *at most* 2 hours out-of-date (the default)? Do you need to do an update before *every* on-demand scan? And why can't that be solved (if it is, in fact, an issue) by increasing the check frequency to, say, every hour? I'm not trying to stifle the idea of distributing the databases via torrent, but some of this discussion seems to be trying to solve a fabricated issue. As for the torrent, I think we can stop the discussion given the following: 1. The ClamAV team has said they will not support torrents. 2. The question about the local directory has been addressed. 3. Torrents can be easily created by anyone. Is there really anything more to discuss, except perhaps some more details of the local directory answer? -- Bryan Burke IT Administrator Department of Electrical Engineering and Computer Science University of Tennessee, Knoxville bbu...@eecs.utk.edu (865) 974-4694 _______________________________________________ Help us build a comprehensive ClamAV guide: visit http://wiki.clamav.net http://www.clamav.net/support/ml
