On Thu, 4 Mar 2004 11:53:32 +0000 (GMT), Andy Fiddaman wrote:
>
> handling application to make a decision about what it lets through.
>
> 0 Not scanned, unable to handle the object.
> 1 Not scanned due to an I/O error.
> 2 Not scanned, as the scanner ran out of memory.
> 3 The object is not of a type the scanner knows. This may
> either mean it was misidentified or that it is cor-
> rupted.
> 4 The object was valid, but encrypted and could not be
> scanned.
> 5 Scanning of the object was interrupted.
> 7 The object was identified as an "innocent" object.
> 9 The object was successfully scanned and nothing was
> found.
> 11 The object is infected.
>
> I'm happy to submit patches but it's difficult without knowing the overall
> direction that the core team want to take.
>
0 as result code should be only used, when everything is ok - no
error or viruses. Otherwise, from the source of clamdscan it seems,
that it has 3 result codes, but I might have missed something:
0 - everything is ok
1 - virus found
2 - error
More verbose result codes would probably be useful for scripting.
--
Virgo Pärna
[EMAIL PROTECTED]
-------------------------------------------------------
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
