So maybe your freshclam isn't telling clamd about the new updates, and
clamd takes a while to notice? I don't know how that situation can be
fixed on a non-debian distro; I've never had the problem myself.
just as FYI, there are 3 ways to make sure clamd knows of db updates done via freshclam:
1. run freshclam with the --daemon-notify option. This will inform clamd to reload right after updates. 2. clamd itself periodically checks for database changes (parameter "SelfCheck" in clamav.conf) and reloads them if neccessary 3. you can restart clamd
------------------------------------------------------- SF.Net is sponsored by: Speed Start Your Linux Apps Now. Build and deploy apps & Web services for Linux with a free DVD software kit from IBM. Click Now! http://ads.osdn.com/?ad_id=1356&alloc_id=3438&op=click _______________________________________________ Qmail-scanner-general mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/qmail-scanner-general
