On Wed, 2004-05-05 at 14:32, Chris Conn wrote: > Tomasz Kojm wrote: > > > > >> Tue May 4 16:08:13 2004 -> Segmentation fault :-( Bye.. > >> > >>and at precisely 16:08:13, MailScanner reports the following virus: > >> > >>May 4 16:08:13 MailScanner[16448]: > >>/var/spool/MailScanner/incoming/16448/.i44K7gOj020343/%nTips.exe: > >>Worm.Klez.H FOUND > >> > >>Is it possible that a %n in the filename (*which is surely illegal*) > >>could cause clamd to crash in such a way? This is obviously the scan > >>that caused the segmentation fault, however is this the reason?
No, it isn't "obviously the scan that caused the segmentation fault". That's a wholly unfounded assumption on your part. > > This server processes between 30 and 100 thousand emails per day, > calling clamdscan on every one. It will find 2 to 5 hundred Klez > viruses per day. In your expert opinion, what would be the reason for > this segmentation fault that occurred at the exact second it scanned > this Klez virus? > Thats unknown. Most likely, one of the other messages being scanned caused a problem. -trog
signature.asc
Description: This is a digitally signed message part
