Hi List
I have a problem with clamd dying without warning. Nothing appears in the log files.
You need to put a watchdog script in place that runs out of cron. Clamd has severe memory management problems and will use all you have - your cron script should look for two things: Is clamd in the proc table, and is the memory size it is using appropriate? I'm using a tcp/ip socket so I poll that as well just to be sure it is not just running but responding. If memory usage grows above 350 meg my script will kill and restart clamd (the memory usage immediately drops below 20 meg). This has been a problem since I began using it at v. 0.65 . I'm currently running CVS from Thursday of last week. It would be nice to avoid needing such a script. Although a watchdog for any critical daemon is a good idea, this one is necessarily brutal.
dp
------------------------------------------------------- This SF.Net email is sponsored by BEA Weblogic Workshop FREE Java Enterprise J2EE developer tools! Get your free copy of BEA WebLogic Workshop 8.1 today. http://ads.osdn.com/?ad_id=4721&alloc_id=10040&op=click _______________________________________________ Clamav-users mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/clamav-users
