Hello again, On Mon, 16 Apr 2012, James B. Byrne wrote:
... I cannot identify any resident filesystem scanner that uses clamd ...
It might not be using clamd directly. There are utilities supplied with ClamAV, one which uses clamd and one which doesn't. 'clamscan' will load the virus database(s) and scan what you tell it to scan. Command line options affect the behaviour of the scanning engine but because clamscan uses the ClamAV libraries, not the clamd daemon (which uses the same libraries), clamd.conf doesn't affect it. Loading the database takes a while so you wouldn't want, for example, to call clamscan repeatedly in a shell script. 'clamdscan' will use clamd, which has already loaded the database(s), to scan what you tell it to scan. The clamd daemon does what it has been configured to do by clamd.conf and command line options have no effect on that. Because clamd has already loaded the database, it is much faster for example to scan the odd file from the command line, although if you gave a command line which told it to scan the entire disc the time to load the database would probably be less important. A shell script which makes many calls to the scanner should probably call clamdscan. It's possible that you have a cron job which is set up to call one of these scanning utilities. -- 73, Ged. _______________________________________________ Help us build a comprehensive ClamAV guide: visit http://wiki.clamav.net http://www.clamav.net/support/ml
