Re: [Clamav-users] Unable to open file or directory ERROR

2004-10-22 Thread Andy Fiddaman
On Thu, 21 Oct 2004, Grant Supp wrote: ; Andy Fiddaman wrote: ; I'm not a developer but this looks similar to what I'm seeing on Solaris. ; Is readdir_r in use here ? (grep READDIR_R clamav-config.h) ; Can you post the dirent struct from your /usr/include/sys/dirent.h file ? ; Otherwise the

Re: [Clamav-users] Unable to open file or directory ERROR

2004-10-22 Thread Tomasz Papszun
On Thu, 21 Oct 2004 at 16:13:41 -0600, Grant Supp wrote: [...] trog wrote: Looks to me that whatever you are using to dissect messages into their parts is creating files with incorrect permissions. It does seem that way, but it only happens for certain files. I've tried all combinations of

Re: [Clamav-users] Unable to open file or directory ERROR

2004-10-21 Thread Trog
On Wed, 2004-10-20 at 16:33, Grant Supp wrote: It seems to happen when scanning the same files. Untitled Attachment seems to cause the problem evey time. I think this attachment might be generated by Outlook 2003 when assigning a task to a user, although I'm not sure, since I don't have a

Re: [Clamav-users] Unable to open file or directory ERROR

2004-10-21 Thread Andy Fiddaman
; On Wed, 2004-10-20 at 16:33, Grant Supp wrote: ; ; It seems to happen when scanning the same files. Untitled Attachment seems to cause the problem evey time. I think this attachment might be generated by Outlook 2003 when assigning a task to a user, although I'm not sure, since I don't have a

Re: [Clamav-users] Unable to open file or directory ERROR

2004-10-21 Thread Grant Supp
Andy Fiddaman wrote: I'm not a developer but this looks similar to what I'm seeing on Solaris. Is readdir_r in use here ? (grep READDIR_R clamav-config.h) Can you post the dirent struct from your /usr/include/sys/dirent.h file ? Otherwise the following command should give enough: find

Re: [Clamav-users] Unable to open file or directory ERROR

2004-10-20 Thread Bogusaw Brandys
Hello, Grant Supp wrote: I'm using Clam AV 0.80 with Qmail-Scanner 1.23 and receive the following lines in my clamd.log: Tue Oct 19 15:22:34 2004 - /var/spool/qmailscan/tmp/newmail01.readyhosting.com109821735148216078/1098217354.16090-1.newmail01.readyhosting.com: Trojan.Dropper.JS.Zerolin-6

Re: [Clamav-users] Unable to open file or directory ERROR

2004-10-20 Thread Grant Supp
Boguslaw Brandys wrote: Is it always when scanning the same files ? Could You try another ? Could You try the same file with OLE2 support disabled ? I'm curious if this is OLE2 related It seems to happen when scanning the same files. Untitled Attachment seems to cause the problem evey

[Clamav-users] Unable to open file or directory ERROR

2004-10-19 Thread Grant Supp
I'm using Clam AV 0.80 with Qmail-Scanner 1.23 and receive the following lines in my clamd.log: Tue Oct 19 15:22:34 2004 - /var/spool/qmailscan/tmp/newmail01.readyhosting.com109821735148216078/1098217354.16090-1.newmail01.readyhosting.com: Trojan.Dropper.JS.Zerolin-6 FOUND Tue Oct 19 15:30:44

Re: [Clamav-users] Unable to open file or directory ERROR

2004-09-23 Thread Grant Supp
Rick Macdougall wrote: Grant Supp wrote: I'm using qmail, qmail-scanner 1.23 and ClamAV 0.75.1 on CentOS 3.1 (recompile of RHEL3.) Ocassionally, I get the Unable to open file or directory ERROR message in my clamd.log. Now I know this sounds like a permissions problem, but bear with me. This

[Clamav-users] Unable to open file or directory ERROR

2004-09-22 Thread Grant Supp
I'm using qmail, qmail-scanner 1.23 and ClamAV 0.75.1 on CentOS 3.1 (recompile of RHEL3.) Ocassionally, I get the Unable to open file or directory ERROR message in my clamd.log. Now I know this sounds like a permissions problem, but bear with me. This only happens sometimes, there are hundreds

Re: [Clamav-users] Unable to open file or directory ERROR

2004-09-22 Thread Rick Macdougall
Grant Supp wrote: I'm using qmail, qmail-scanner 1.23 and ClamAV 0.75.1 on CentOS 3.1 (recompile of RHEL3.) Ocassionally, I get the Unable to open file or directory ERROR message in my clamd.log. Now I know this sounds like a permissions problem, but bear with me. This only happens sometimes,