[Clamav-users] clamav-milter 0.85.1 processes not going away

2005-05-28 Thread N Fung
Hi! Ever since upgrading to 0.85.1, some clamav-milter processes don't seem to know when to exit/go away. A 'ps -aux' would show something like this: 15159 ?? Ss 0:00.30 (clamav-milter) 15160 ?? Ss 0:00.30 (clamav-milter) 15161 ?? Ss 0:00.30 (clamav-milter) 15162 ?? Ss

Re: [Clamav-users] clamav-milter 0.85.1 processes not going away

2005-05-28 Thread N Fung
Hi again! I forgot to mention that all those persistent clamav-milter processes would go into a zombie (?) state after recording these in /var/log/mailllog: Milter (clmilter): timeout before data read Milter (clmilter): to error state Milter: data, reject=451 4.3.2 Please try again later

[Clamav-users] Re: Memory limit per process hit

2005-05-28 Thread G.W. Haywood
Hi there, On Fri, 27 May 2005 Pablo Alsina wrote: > We added a sort of tarpitting solution to our sendmail... > clamav-milter seems to be suffering. What happens is that the > maximum number of childs are reached in a 2-4 hour period People with far more experience than I tell me that this isn't

[Clamav-users] Re: Spam from ClamAv digest lists.

2005-05-28 Thread G.W. Haywood
Hi there, On Sat, 28 May 2005 Robert L Mathews wrote: > "G.W. Haywood" <[EMAIL PROTECTED]> wrote: > > > They are spamming me. > > Uh, well, that's not "spam" (since it's not "unsolicited"). Well that depends on how you define "unsolicited". :) I asked for the digests to get less mail not more,

Re: [Clamav-users] Re: Memory limit per process hit

2005-05-28 Thread Matt Fretwell
G.W. Haywood wrote: > > We added a sort of tarpitting solution to our sendmail... > > clamav-milter seems to be suffering. What happens is that the > > maximum number of childs are reached in a 2-4 hour period > > People with far more experience than I tell me that this isn't the > way. And th

Re: [Clamav-users] clamav-milter 0.85.1 processes not going away

2005-05-28 Thread N Fung
Found many of these in /var/log/clamd.log Sat May 28 19:56:58 2005 -> /var/tmp/clamav-c110c22fa52c87f5/msg.rMYrWH: Worm.Mytob.BN-1 FOUND LibClamAV Error: Segmentation fault :-( Bye.. Sat May 28 19:57:16 2005 -> /var/tmp/clamav-c110c22fa52c87f5/msg.9vy1YC: Worm.Mytob.BN-1 FOUND LibClamAV Error: Seg

Re: [Clamav-users] Configuring clamd.conf

2005-05-28 Thread Lee Zelyck
# By default clamd uses scan options recommended by libclamav. This option # disables recommended options and allows you to enable selected ones below. # DO NOT TOUCH IT unless you know what you are doing. # Default: disabled #DisableDefaultScanOptions > > Before one of the trolls jumps at this,

Re: [Clamav-users] Configuring clamd.conf

2005-05-28 Thread Matt Fretwell
Lee Zelyck wrote: > # Default: enabled > #ScanOLE2 ^^^ As you can see, the comments mention what the default is :) > Do I need to Uncomment '#DisableDefaultScanOptions' > and '#ScanOLE2' to get it to scan for OLE2's, or by > doing nothing, Clam will Scan for OLE2's by default. If you wa

Re: [Clamav-users] Configuring clamd.conf

2005-05-28 Thread Lee Zelyck
Hi all, > > # Default: enabled > > #ScanOLE2 ^^^ > > As you can see, the comments mention what the > default is :) > Yes, thats what I had suspected, but I just wanted to make sure. Thank you for your help! Lee > > Do I need to Uncomment > '#DisableDefaultScanOptions' > > and '#ScanOLE

[Clamav-users] Output Errors From Clam-0.85.1 Startup

2005-05-28 Thread Lee Zelyck
Greetings all, Well, I think I have the install working, but I have a small lingering concern: # /etc/init.d/clamav start Starting Antivirus database update daemon. Starting Antivirus daemon. Starting E-mail scanner. /usr/local/sbin/clamav-milter: (-q && !LogSyslog): warning - all interception me

Re: [Clamav-users] Output Errors From Clam-0.85.1 Startup

2005-05-28 Thread Matt Fretwell
Lee Zelyck wrote: > Well, I think I have the install working, but I have a > small lingering concern: > > # /etc/init.d/clamav start > Starting Antivirus database update daemon. > Starting Antivirus daemon. > Starting E-mail scanner. > /usr/local/sbin/clamav-milter: (-q && !LogSyslog): > warning