On 4/30/2015 10:06 AM, John McGowan wrote: >> clamdscan scanning is made by clamd, this process use to run with non-root >> privileges > > Knowing that I wanted clamd to be able to scan any part of the file > system, I did reconfigure clamd to run as root by commenting out the > config param that change the user that clamd ran as. > > So I don't think this issue is permissions related. But I could still > be wrong. > > I tried it without changing who clamd was running as and got > completely different permissions errors than what I'm seeing now. > > /John
I strongly suggest using clamscan rather than clamdscan for system scanning. The performance advantage of clamd and its pre-loaded databases is largely irrelevant when scanning a large number of files and you won't have permission problems. You also avoid running clamd with root permissions, which is potentially unsafe. In some cases, using clamscan may actually be faster than clamdscan. _______________________________________________ Help us build a comprehensive ClamAV guide: https://github.com/vrtadmin/clamav-faq http://www.clamav.net/contact.html#ml
