>> The second symptom is from not running clamd, or having
>> a wrong path to clamav's config file in freshclam.conf.
>> If you don't have clamd running (which I recommend),
>> comment out the
>> NotifyClamd <clamav config file>
>> or make sure the argument to NotifyClamd correctly
>> points to clamd's config file.
>
> OK. How do I run clamd?
> Do I only need to issue the command "clamd" and that's it?
> After that will I have on-access protection?
> If I reboot the PC, will clamd shutdown itself
> gracefully, or do I first need to send some command so
> clamd deactivates itself correctly (not leaving sockets
> opened like Haywood said)??
>
No. There should be a startup script like
/etc/init.d/clamd
or
/etc/init.d/clamav-daemon
which should be run automatically when the system starts and stops. The normal
*nix way.
_______________________________________________
Help us build a comprehensive ClamAV guide: visit http://wiki.clamav.net
http://www.clamav.net/support/ml
