At 12:54 PM 6/10/2005, you wrote:
* [EMAIL PROTECTED] <[EMAIL PROTECTED]> [20050610 22:49]: wrote:
> At 10:44 AM 6/10/2005, you wrote:
>
> >Problems with 0.85.1 seem to be confined to FreeBSD.
> >Anything interesting in /var/log/clamd.log?
>
> nothing interesting. records of viruses found, and the startup
> logging. that's it.
>
> i've adjusted the number of concurrent connections inbound to the
> AS/AV server, and that seems to have helped somewhat.
What is that adjustment supposed to do/achieve?
to try to alleviate the problem described. absent a known cause, one
experiments, does one not?
If your server is a busy one, you may try increasing the MaxThreads
value in clamd.conf. It's worked for me.
as i mentioned, clamd 0.85.1 has been working fine for me as well, up
until a few days ago when this issue arose. here's my clamd.conf:
LogFile /var/log/clamd.log
LogFileMaxSize 15M
LogTime
LogSyslog
LogFacility LOG_LOCAL6
PidFile /var/run/clamd/clamd.pid
LocalSocket /tmp/clamd
FixStaleSocket
MaxConnectionQueueLength 60
StreamMaxLength 100M
MaxThreads 10
ReadTimeout 300
IdleTimeout 120
MaxDirectoryRecursion 20
SelfCheck 600
User qscand
Also, think about the size of messages you send to clamd. In my case,
I only send stuff that is less than 2MB in size. If they make a virus
larger than that, my users will get it hands down ;-)
and what of a virus zipped into a larger zip file? Since the largest
message we'll accept is 100M, then that's what my StreamMaxLength is
set at, per the comments in clamd.conf. on the other hand, it would
take an awfully determined virus distributed to put their virus in
such a large message.....
Paul Theodoropoulos
http://www.anastrophe.com
http://www.smileglobal.com
_______________________________________________
http://lurker.clamav.net/list/clamav-users.html
