Watchdog('clamav', 'Uploaded file %filename could not be scanned.
The actual result of clamscan is assigned to $result: The lines of text output by clamscan are assigned as an array to $output The actual output from clamscan is discarded and only the return code is logged: // exec: Therefore when something goes wrong, the module typically records very little information e.g.
The man page now just says this: RETURN CODES but they were replaced by the catch-all return code 2 in the next release 0.96 (from 2010): Looking at the source code for the clamav project itself, the detailed error messages were present in the man page in release 0.95 (from 2009): However, it looks like clamscan changed the way it reports errors some time ago: the switch/case based on the return code from the executable is based on the return code being something like the above. * 64: Can't write to temporary directory (please specify another one). * 63: Can't create temporary files/directories (check permissions). * 58: I/O error, please check your file system. * 57: Can't get absolute path name of current working directory.
* clamscan return values (documented from man clamscan) It looks like the executable mode code was written when clamscan used to provide rich information about errors in its return codes: /**
0 kommentar(er)
