Date: Wed, 16 Dec 2009 05:32:32 -0500 From: Tom Shaw <ts...@oitc.com> Subject: Re: [Clamav-users] ExcludePath, defining absolute path To: ClamAV users ML <clamav-users@lists.clamav.net> Message-ID: <p062408c0c74e67624...@[10.0.3.10]> Content-Type: text/plain; charset="us-ascii" ; format="flowed"
At 6:11 AM +0000 12/16/09, dev.ad...@ntlworld.com wrote:
Hi, I know this is an old topic that seems to have caused some problems in the past and has apparently been fixed in version .3, but I still can't get it to work. I'm using OSX and I would like to scan the boot volume but one of the directories is called 'Volumes' which contains directories and links to other volumes which I scan separately. Is it possible to exclude an absolute path using the configure variable ExcludePath? A.
A. Why don't you just do something like sudo clamscan / Tom Thanks for reply Tom. This is the way that I've setup the scan, using clamdscan, for the boot volume. Unfortunately, there is a sub-directory called /Volumes in the root directory that contains partitions and all external storage devices that are mounted. Think it's an OSX issue. clamd assumes that it is part of the scan objective and proceeds to cycle through *every* single device. The scan strategy I've adopted is to scan some partitions or volumes more regularly than others based on usage or exposure. There is a --file-list option with clamdscan but I feel that for a general scan it isn't the ideal solution. Not to mention maintaining the file. Andy. _______________________________________________ Help us build a comprehensive ClamAV guide: visit http://wiki.clamav.net http://www.clamav.net/support/ml
