1, 2) Both clamd and clamav-milter are built from 0.70RC (stock built from Petr Kristof's RedHat SPEC file).
3) No I don't, I will. I am seeing the following in clamd.log: WARNING: ScanStream: Size exceeded (stopped at 10461493, max: 10485760) and this in /var/log/messages: clamav-milter: ClamAv, mi_rd_cmd: read returned -1: Connection reset by peer and this in /var/log/maillog: SYSERR(root): out of memory: Cannot allocate memory I am seeing a huge number of the "Cannot allocate memory" messages, many many more than the clamd & clamav-milter mesages (which correspond to each other). Although I believe the "Cannot allocate memory" messages are related to this problem. Many thanks. Andrew > Subject: Re: [Clamav-users] Behaviour of "StreamMaxLength" > On Wednesday 07 Apr 2004 7:41 pm, Andrew Chan wrote: > > I am not sure I understand "StreamMaxLength". > > > > I am using clamav-milter (sendmail) and I've set "StreamMaxLength 10M". > > 1) What version of clamd (clamscan -V) > 2) What version of clamav-milter (clamav-milter --version) > 3) Do you have LogSysLog enabled in clamav.conf, and if so > are you seeing entries of this form in your syslog? > Message more than StreamMaxLength (%ld) bytes - not scanned > > > Andrew ------------------------------------------------------- This SF.Net email is sponsored by: IBM Linux Tutorials Free Linux tutorial presented by Daniel Robbins, President and CEO of GenToo technologies. Learn everything from fundamentals to system administration.http://ads.osdn.com/?ad_id=1470&alloc_id=3638&op=click _______________________________________________ Clamav-users mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/clamav-users
