On Thu, 2009-03-05 at 19:07 -0800, Bill Landry wrote: > Chris wrote: > > On Thu, 2009-03-05 at 20:33 -0600, Brandon Perry wrote: > >> Make sure clamd has permission to read the file :-) > >> > > > > -rwxr-xr-x 1 root root 228068 2009-03-05 17:42 /usr/local/bin/clamdscan* > > > > Odd clamscan works fine: > > > > -rwxr-xr-x 1 root root 131462 2009-03-05 17:42 /usr/local/bin/clamscan* > > > > so why doesn't clamdscan work or am I missing something here? > > Like Brandon said, make sure the clamdscan has permissions to read the > file. That's because clamdscan (and clamd) run as whatever user you've > defined in your clamd.conf file. OTH, clamscan runs with whatever > permissions you have. If you are logged on as root, than clamscan will > run as root and can read any file. > > Bill
This is the setting in my clamd.conf: # Run as another user (clamd must be started by root for this option to work) # Default: don't drop privileges User clamav Please disregard, I apparently needed to refresh myself with the clamdscan manpage: [ch...@localhost ~]$ clamdscan -<spam1.txt fd[12]: OK ----------- SCAN SUMMARY ----------- Infected files: 0 Time: 0.002 sec (0 m 0 s) works fine. Dumbness on my part. -- KeyID 0xE372A7DA98E6705C
signature.asc
Description: This is a digitally signed message part
_______________________________________________ Help us build a comprehensive ClamAV guide: visit http://wiki.clamav.net http://www.clamav.net/support/ml
