On Thu, 12 Feb 2004, Morris Jones wrote:
> 2. I tested the clam command line from shell with my test email using
> both clamscan and clamdscan. Clamscan properly reports the virus.
> Clamdscan reports a clean message. I used the same arguments for both.
>
> Mojo
They -should- return the same result, with the same args and same input.
Are you sure that your clamscan and clamd are built from the same kit
and looking at the same ".cvd" files?
One other possibility, a permissions issue.
Note that "clamscan" runs with the UID of the invoker whereas the
"clamd" runs with the UID configured in the clamav.conf file
(the 'User' parameter, by default "clamav").
Thus the "clamav" user needs read permissions on the file for the
clamdscan to work.
For testing, you can add the "--debug" argument to clamscan
to see what it's doing. It doesn't do anything for clamdscan,
as clamd is doing the work. You will have to turn on "Debug"
in the clamav.conf file (probably also want to turn on "Forground"
and restart clamd in a window to watch the output).
--
Dave Funk University of Iowa
<dbfunk (at) engineering.uiowa.edu> College of Engineering
319/335-5751 FAX: 319/384-0549 1256 Seamans Center
Sys_admin/Postmaster/cell_admin Iowa City, IA 52242-1527
#include <std_disclaimer.h>
Better is not better, 'standard' is better. B{
