On Thu, 2005-03-17 at 04:32 -0800, Mark Pizzolato wrote:
> I believe his app is timing out, and that is probably a good thing. In
> clamav 0.83
> the behavior of clamd would cause long delays when a database reload was
> needed.
If *could* cause a long delay, under specific circumstances. But
On Thursday, March 17, 2005 at 3:26 AM, Maxim Dounin etote:
It looks like your client issues STREAM command to clamd, and not
connects to port replied.
This may happen due to timeouts in your client. I.e.: your client
connects, issues STREAM, then clamd waits for free working thread, your
client ti
Hello!
It looks like your client issues STREAM command to clamd, and not
connects to port replied.
This may happen due to timeouts in your client. I.e.: your client
connects, issues STREAM, then clamd waits for free working thread, your
client timeouts, clamd's working threads opens sockets and
On Thu, 2005-03-17 at 10:31 +, Colin MacDonald wrote:
> I've seen the following in clamd logs and it looks like some kind of bug:
>
> Wed Mar 16 15:40:02 2005 -> Reading databases from /usr/local/clamav/db
> Wed Mar 16 15:40:03 2005 -> Database correctly reloaded (31605 viruses)
> Wed Mar 16
Hi.
I've seen the following in clamd logs and it looks like some kind of bug:
Wed Mar 16 15:40:02 2005 -> Reading databases from /usr/local/clamav/db
Wed Mar 16 15:40:03 2005 -> Database correctly reloaded (31605 viruses)
Wed Mar 16 15:42:03 2005 -> ERROR: ScanStream: accept timeout.
Wed Mar 16 15:
