It uses TCP/IP to communicate, so clamd has to be listening on 127.0.0.1 on the default port. The overhead of the check is simply the overhead of issuing a PING command to clamd, which should be minimal I would think.
Bret Phil (Medway Hosting) wrote: > ----- Original Message ----- > From: "Bret Miller" <[EMAIL PROTECTED]> > To: <[email protected]> > Sent: Tuesday, August 26, 2008 7:29 PM > Subject: Re: [clamav-win32] Clamd terminating (Malformed database) > > > >> You could try my service app (requires .NET 1.1 framework). The service >> program monitors clamd to make sure it stays running, and restarts it if >> not. >> *http://mail.wcg.org/~postmaster/ClamAVService_Setup.exe* >> > > Many thanks for that. I may well try it, if I can't find the reason for the > crashing. > > What is the overhead of checking clamd is running more regularly (e.g. 10 > seconds instead of the default 30 ?) > > All the best > > Phil > > > _____________________________________________ > > Website Hosting from only £5.00 per month. > www.medwayhosting.com - +44 (0)1634 856965 > _____________________________________________ > > Digital & Traditional Printing, and much more > www.medwayprint.com - +44 (0)1634 281199 > _____________________________________________ > _______________________________________________ > http://lists.clamav.net/cgi-bin/mailman/listinfo/clamav-win32 > _______________________________________________ http://lists.clamav.net/cgi-bin/mailman/listinfo/clamav-win32
