Re: [SLUG] clamdscan failing
1. i am not sure about qmail-queue-scanner.pl so don't know your problem here. but if you want to scan all you incoming email, there is a mail scanner called amavis, it can use clamdscan as the anti-virus engine. 2. maybe you want to check your /etc/clamd.conf file and change the user from clamav to root. regards J Ai Peter Rundle wrote: Sluggers, just wondering if anyone can help out with a clamdscan problem. I'm using clamscan to scan incomming e-mails under qmail-queue-scanner.pl and it's all working fine detecting virii etc except for the fact that it takes around 2 secs to do the scan. So I wanted to use clamdscan (the front end to clamd) but it fails with this error Can't access the file ERROR If I run it on the command line #> clamdscan msg.pif /root/msg.pif Can't access the file ERROR (yes the file exists with 744 permissions) Ok, so I appear to have some sort of permission problem but I can't figure it out, same error occurs in all directories and with non-root users. any cluesticks? (Fedora core btw) TIA's P. -- SLUG - Sydney Linux User's Group Mailing List - http://slug.org.au/ Subscription info and FAQs: http://slug.org.au/faq/mailinglists.html
Re: [SLUG] clamdscan failing
clamdscan failing? maybe it clammed up! Stuart. Find local movie times and trailers on Yahoo! Movies. http://au.movies.yahoo.com -- SLUG - Sydney Linux User's Group Mailing List - http://slug.org.au/ Subscription info and FAQs: http://slug.org.au/faq/mailinglists.html
Re: [SLUG] clamdscan failing
John Clarke wrote: Are you running clamd as root or as a non-privileged user? Is the directory containing the file readable by that user? /root is normally only readable by root. The solution, if you're running clamd as a non-privileged user, is to put the files into a directory that the clamd user can read and scan them from there. Hi John, that's got it sorted, turned out to be a bit of a comedy of errors. I edited the /etc/clamav.conf file and changed the User to qscand but that didn't fix it when I was testing on the command line. Turned out that's because the file must be specified by it's full path so that clamd can find it. Thanks for the info, I think I'm sorted now. Cheers P. -- SLUG - Sydney Linux User's Group Mailing List - http://slug.org.au/ Subscription info and FAQs: http://slug.org.au/faq/mailinglists.html
Re: [SLUG] clamdscan failing
On Fri, Apr 30, 2004 at 01:49:58PM +1000, Peter Rundle wrote:
>Can't access the file ERROR
This message only appears in the source (I'm looking at clamav-0.70-rc
but it's probably the same in other versions) in one place in
clamd/scanner.c:
/* check permissions */
if(access(filename, R_OK)) {
mdprintf(odesc, "%s: Can't access the file ERROR\n", filename);
return -1;
}
> #> clamdscan msg.pif
> /root/msg.pif Can't access the file ERROR
>
> (yes the file exists with 744 permissions)
Are you running clamd as root or as a non-privileged user? Is the
directory containing the file readable by that user? /root is normally
only readable by root.
The solution, if you're running clamd as a non-privileged user, is to
put the files into a directory that the clamd user can read and scan
them from there.
Cheers,
John
--
I must be looking senile. Everyone's telling me what to do, when I
already know. Nod and smile, nod and smile, think, "fuck off".
-- John the Unstable
--
SLUG - Sydney Linux User's Group Mailing List - http://slug.org.au/
Subscription info and FAQs: http://slug.org.au/faq/mailinglists.html
[SLUG] clamdscan failing
Sluggers, just wondering if anyone can help out with a clamdscan problem. I'm using clamscan to scan incomming e-mails under qmail-queue-scanner.pl and it's all working fine detecting virii etc except for the fact that it takes around 2 secs to do the scan. So I wanted to use clamdscan (the front end to clamd) but it fails with this error Can't access the file ERROR If I run it on the command line #> clamdscan msg.pif /root/msg.pif Can't access the file ERROR (yes the file exists with 744 permissions) Ok, so I appear to have some sort of permission problem but I can't figure it out, same error occurs in all directories and with non-root users. any cluesticks? (Fedora core btw) TIA's P. -- SLUG - Sydney Linux User's Group Mailing List - http://slug.org.au/ Subscription info and FAQs: http://slug.org.au/faq/mailinglists.html
