On Tue, 4 Nov 2003, Tomasz Kojm wrote:
> On Mon, 3 Nov 2003 13:35:50 -0500 (EST)
> Ed Phillips <[EMAIL PROTECTED]> wrote:
>
> > clamscan detects the "broken on purpose" ZIP files and reports an
> > error message (correctly), when you scan the ZIP file directly or when
> > you scan the directory containing the broken ZIP file. clamd, however,
> > ignores all errors while scanning a directory hierarchy, so in the
> > case where it's scanning a directory that contains only the broken ZIP
> > file, you get an OK message from clamd (very broken behavior IMO!).
>
> This is already fixed in CVS:
>
> Sun Oct 26 06:26:14 CET 2003 (tk)
> ---------------------------------
> * clamd: report file errors with CONTSCAN (suggested by Daniel Fraga)
>
> > Yes, I know 20030317 is very old, but it has stayed running since the
> > time we installed it, and the more current snapshots of clamd crash
> > pretty quickly for us. And, it appears clamd still works the same way
>
> 20030317 contains _two_ dangerous race conditions and I don't believe
> it's stable.
Well, it has been running for us for several months in a row under severe
load... I'd call that pretty "stable" in my book. Besides, bug-fix or
not, the current "stable" release (0.60) couldn't even stay running for a
few hours under the same load... which I call "ridiculously unstable".
The current snapshot is giving us compiler grief... yet more gcc-isms...
doesn't want to compile with Sun Forte...
Ed
Ed Phillips <[EMAIL PROTECTED]> University of Delaware (302) 831-6082
Systems Programmer III, Network and Systems Services
-------------------------------------------------------
This SF.net email is sponsored by: SF.net Giveback Program.
Does SourceForge.net help you be more productive? Does it
help you create better code? SHARE THE LOVE, and help us help
YOU! Click Here: http://sourceforge.net/donate/
_______________________________________________
Clamav-users mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/clamav-users
