I would suggest to check the log for errors. Also you can use 'monit' monitor clamd, it can watch the mem usage as well as the clamd daemon. http://www.tildeslash.com/monit
They have examples here; http://www.tildeslash.com/monit/examples.html#clamavd You can also use clamdwatch which is included in the clamav package. Hth, -rich -----Original Message----- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] Behalf Of K. Shantanu Sent: Monday, May 17, 2004 12:52 PM To: [EMAIL PROTECTED] Subject: [Clamav-users] clamd dying: reasons Hi, Are there any particular reasons why clamd might die all of sudden? It happens to me atleast once a week. And then I have to many a times remove the clamd file and restart clamd. And the worst part is that my messages starts bouncing if clamd dies stating that it cannot connect to clamd. What do you guys do in this suitation other than running under daemontools? I am more worried about the clamd socket which persist even when clamd dies. Is there a way I can tell clamd not to look at that and what are the disadvantages of this? Thanks a lot. Cheers, Shantanu ------------------------------------------------------- This SF.Net email is sponsored by: SourceForge.net Broadband Sign-up now for SourceForge Broadband and get the fastest 6.0/768 connection for only $19.95/mo for the first 3 months! http://ads.osdn.com/?ad_id=2562&alloc_id=6184&op=click _______________________________________________ Clamav-users mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/clamav-users ------------------------------------------------------- This SF.Net email is sponsored by: SourceForge.net Broadband Sign-up now for SourceForge Broadband and get the fastest 6.0/768 connection for only $19.95/mo for the first 3 months! http://ads.osdn.com/?ad_id=2562&alloc_id=6184&op=click _______________________________________________ Clamav-users mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/clamav-users
