Sean McGlynn wrote: > Just to be certain (It's not my first day with Linux, but I'm still > relatively new > to it), you mean NFS as in Network File System, as in mounting a remote file > system on the Linux server, correct? If correct, then no, NFS is not > involved. > Both the directory being scanned and the destination directory for quarantine > files on on the root filesystem, local to the machine. >
Yes - that is what I meant. To just cut to the chase, the diagnostics I have followed here are: clamscan is working perfectly but there is a problem with permissions (examples: root and NFS, non-root and insufficient access privs). Those have been ruled out. Next are: source and destination for all paths exist and are on local, not NFS storage (including NAS storage which is typically NFS). It is assumed you have room on disk to put the things you are trying to quarantine. If you are using quotas then that is also a consideration. As a test you can always try to move a file from the source to the destination using the command line as that is all that clamscan would do, and that just may reveal something unexpected. Still assuming nothing is wrong with clamscan and the file paths and permissions are good you are next left to trace clamscan as has been suggested. That moves us closer to a situation where clamscan is not healthy. If strace shows file handling errors then there is probably something wrong with the build. To my knowledge there is nothing wrong with the software design in this regard. Finally, if there are no strace errors then we are left with a situation where something you are sure of is wrong. Happens to me all the time. dp _______________________________________________ Help us build a comprehensive ClamAV guide: visit http://wiki.clamav.net http://lurker.clamav.net/list/clamav-users.html
