On Jul 6, 2010, at 4:51 PM, Noel Jones wrote: > Make sure you restart clamd after editing clamd.conf.
Ah, this was the core of my problem. Clamd was not seeing the new VirusEvent command lines I was using for testing. My config file was not really being reloaded. I was starting/stopping clamd like this, in order to reload the config: sudo launchctl stop com.clamd.daemon sudo launchctl start com.clamd.daemon But this doesn't work. What I need to do to reload the configuration is: sudo launchctl unload -w /Library/LaunchDaemons/com.clamxav.clamd.plist Kill [clamv process ID] sudo launchctl load -w /Library/LaunchDaemons/com.clamxav.clamd.plist These three steps above will cause the config file to be reloaded. Of course you can also reboot the machine but sometimes this is not a good option. Is there a better way to force the config file to be reloaded? I don't like the Kill step, but it seems to be necessary. And as a follow-up, the VirusEvent will run a console app. I am grateful for the help, thank you! Russ _______________________________________________ Help us build a comprehensive ClamAV guide: visit http://wiki.clamav.net http://www.clamav.net/support/ml
