On Fri, Jun 21, 2013 at 7:28 AM, Andreas Schulze
wrote:
> I agree if freshclam load a *new* db in case of a *new* pattern version
> to verify the data are valid. But if no update was available, thats total
> unnecessary!
>
> Is there any clamav developer who could point me into the code or explain
Am 10.04.2013 15:05 schrieb Andreas Schulze:
> symptom: freshclam needs 3..4 seconds to finish also in the case where *no*
> updates are available.
No comments on this topic anymore...
Thats worse because freshclam still steal cputime here :-(
To dive into the problem I describe the problem agai
Am 12.04.2013 11:19 schrieb Chuck Swiger:
> The data available to me suggests that ClamAV has seen ~736 database updates
> since the beginning of the year, for an average update frequency of ~3.5
> hours between updates.
that fine. I could update not once a minute but every three hours.
But in th
Am 12.04.2013 20:27 schrieb Matus UHLAR - fantomas:
> On 12.04.13 19:58, Andreas Schulze wrote:
> >But back to my main problem. clamscan wastes 3 seconts time
> >loading the complete engine every time it is called.
>
> loading virus databage to memory and parsing it is really CPU-intensive
> proce
On 12.04.13 19:58, Andreas Schulze wrote:
But back to my main problem. clamscan wastes 3 seconts time loading
the complete engine every time it is called.
loading virus databage to memory and parsing it is really CPU-intensive
process. That's why we recommend running clamd daemon and using clam
Hi--
On Apr 12, 2013, at 10:58 AM, Andreas Schulze wrote:
> But back to my main problem. clamscan wastes 3 secon[d]s time loading the
> complete engine every time it is called.
> Notice the timestamps!
The data available to me suggests that ClamAV has seen ~736 database updates
since the beginn
Am 11.04.2013 15:50, schrieb Greg Folkert:
Is that checking your *OWN* mirror? If not, you are being throttled.
sure, I ask my own server of course.
But back to my main problem. clamscan wastes 3 seconts time loading the
complete engine every time it is called.
Notice the timestamps!
# echo
On Thu, 2013-04-11 at 15:20 +0200, Andreas Schulze wrote:
> Am 10.04.2013 17:39, schrieb Al Varnell:
> > I thought the limit was four times an hour. Is that only for mirror
> > servers?
> cat /etc/cron.d/clamav
> * * * * * root freshclam
>
> :-)
Is that checking your *OWN* mirror? If not, you a
Am 10.04.2013 17:39, schrieb Al Varnell:
> I thought the limit was four times an hour. Is that only for mirror servers?
cat /etc/cron.d/clamav
* * * * * root freshclam
:-)
___
Help us build a comprehensive ClamAV guide: visit http://wiki.clamav.net
http
On 4/10/13 6:05 AM, "Andreas Schulze" wrote:
> I configured freshclam to not lookup the dns for existance of a new
> patternversion. Instead freshclam contacts the
> clamav-server and fire up HTTP Head queries. That way I could let run
> freshclam once a minute.
>
I thought the limit was four ti
Hello,
I configured freshclam to not lookup the dns for existance of a new
patternversion. Instead freshclam contacts the
clamav-server and fire up HTTP Head queries. That way I could let run freshclam
once a minute.
Because I run a clamav-mirror in my local network, that's not a problem.
But I
11 matches
Mail list logo
