Re: [Clamav-users] nonblock_connect: connect timing out (30 secs)

2009-09-28 Thread Agostinho Carvalho
> From: ja...@iki.fi > To: clamav-users@lists.clamav.net > Date: Mon, 28 Sep 2009 20:37:54 +0300 > Subject: Re: [Clamav-users] nonblock_connect: connect timing out (30 secs) > > >>> > >>> Hello, > >>> > >>> But do I really ne

Re: [Clamav-users] nonblock_connect: connect timing out (30 secs)

2009-09-28 Thread Jari Fredriksson
>>> >>> Hello, >>> >>> But do I really need clamd?? >>> As far as I can tell, clamd "only" gives me on-access >>> protection, right? >>> >>> Thank you >>> Agostinho >>> >> >> No, clamd does not give to transparent backgroup >> protection, like the Windows antivirus tools to. It is a >> daemoni

Re: [Clamav-users] nonblock_connect: connect timing out (30 secs)

2009-09-28 Thread Agostinho Carvalho
> From: ja...@iki.fi > To: clamav-users@lists.clamav.net > Date: Mon, 28 Sep 2009 19:50:56 +0300 > Subject: Re: [Clamav-users] nonblock_connect: connect timing out (30 secs) > > >> From: ja...@iki.fi > >> To: clamav-users@lists.clamav.net > >

Re: [Clamav-users] nonblock_connect: connect timing out (30 secs)

2009-09-28 Thread Jari Fredriksson
>> From: ja...@iki.fi >> To: clamav-users@lists.clamav.net >> Date: Sun, 27 Sep 2009 22:55:31 +0300 >> Subject: Re: [Clamav-users] nonblock_connect: connect >> timing out (30 secs) >> >>>> The second symptom is from not running clamd, or hav

Re: [Clamav-users] nonblock_connect: connect timing out (30 secs)

2009-09-28 Thread Agostinho Carvalho
> From: ja...@iki.fi > To: clamav-users@lists.clamav.net > Date: Sun, 27 Sep 2009 22:55:31 +0300 > Subject: Re: [Clamav-users] nonblock_connect: connect timing out (30 secs) > > >> The second symptom is from not running clamd, or having > >> a wrong path to clama

Re: [Clamav-users] nonblock_connect: connect timing out (30 secs)

2009-09-27 Thread Jari Fredriksson
>> The second symptom is from not running clamd, or having >> a wrong path to clamav's config file in freshclam.conf. >> If you don't have clamd running (which I recommend), >> comment out the >> NotifyClamd >> or make sure the argument to NotifyClamd correctly >> points to clamd's config file.

Re: [Clamav-users] nonblock_connect: connect timing out (30 secs)

2009-09-27 Thread Agostinho Carvalho
Hello Thomas > This is normal behavior, since the mirror 82.195.234.148 is down, freshclam > retries from a different mirror. > Freshclam should blacklist this IP somehow (haven't read the source for a > while, blame me). Also the clamav team removes mirrors which are out of sync > or do

Re: [Clamav-users] nonblock_connect: connect timing out (30 secs)

2009-09-27 Thread Thomas Lamy
Agostinho Carvalho wrote: > > Hello. > > New Clam user here, so please be gentile :-) > Recently (since 4 days ago or so), I've been having some > issues while updating my virus definitions. > > Here is the terminal output after a freshclam command: > > > ClamAV update process started at Sun

[Clamav-users] nonblock_connect: connect timing out (30 secs)

2009-09-27 Thread G.W. Haywood
Hi there, On Sun, 27 Sep 2009 Agostinho Carvalho wrote: > New Clam user here, so please be gentile :-) Er, gentle. I'll try. :) > WARNING: Clamd was NOT notified: Can't connect to clamd through > /var/lib/clamav/clamd-socket > connect(): No such file or directory The 'clamd' daemon can list

[Clamav-users] nonblock_connect: connect timing out (30 secs)

2009-09-27 Thread Agostinho Carvalho
Hello. New Clam user here, so please be gentile :-) Recently (since 4 days ago or so), I've been having some issues while updating my virus definitions. Here is the terminal output after a freshclam command: ClamAV update process started at Sun Sep 27 08:41:39 2009 main.cvd is up to dat