Hi, On 3 apr. 2013, at 03:05, Jim Preston <jimli...@commspeed.net> wrote:
> On 03/25/2013 09:26 AM, Ben Stuyts wrote: >> Well, still no luck, same errors over the weekend. Anybody have any other >> ideas? >> >> Thanks, >> Ben >> >> On 22 mrt. 2013, at 18:43, Ben Stuyts <b...@altesco.nl> wrote: >> > [snip] >> (cmd line is >> /usr/local/bin/clamdscan -m --fdpass /home) > [snip] > > This is not a solution but a thought on pointing to root cause. From your > original post, I gather that there are multiple users on the system. What > happens if you scan each user individually? If it is always the same user's > directory causing the problem, you can then narrow the scan down to get the > exact directory / file(s) to get to exact cause. > > If scans are automated, i.e. being down after hours when no one is there, > there are numerous ways to automate the individual scans to help get a handle > on the cause of the problem. The exact methods might be platform dependent > and somewhat OT for this particular thread. Feel free to email me off-list if > you want to discuss any methods. By automation and OT, I am referring to > using scripting and / or cron to do the automation and not anything inside of > ClamAV itself. It is indeed a whole bunch of home directories from different users. I'll give it a try to scan each one separately and narrow it down. Ben _______________________________________________ Help us build a comprehensive ClamAV guide: visit http://wiki.clamav.net http://www.clamav.net/support/ml
