Török Edwin wrote: > On 2009-03-04 19:44, Dennis Peterson wrote: >>> >> Is there not a "nice" way to do this? > > 0.95rc1 does reload "nicer", in the sense that it accepts new > connections while reloading the DB. > Reloading the database should take about a second. Using anything less > than 100% CPU wouldn't be possible, it would just make loading the > database longer.
Maybe I'm not interpreting this as it would... This is a Sun T2000 8 cores, with 8 GB memory. So, this isn't a very small computer. From clamd logs, I have this. Wed Mar 4 11:59:36 2009 -> SelfCheck: Database modification detected. Forcing reload. Wed Mar 4 11:59:36 2009 -> Reading databases from /opt/clamav/db Wed Mar 4 11:59:51 2009 -> Database correctly reloaded (514191 signatures) Wed Mar 4 11:59:51 2009 -> WARNING: lstat() failed on: /var/spool/jchkmail/49AE5F17.000.0000 So, between 11:59:36 and 11:59:51, there are 17 seconds, and not 1 second. The next line, is interesting too - the one with a "lstat() failed". That means : the clamd client (a milter) connected to clamd and wait 10 seconds for an answer and gave up, removing the spool file. clamd in fact accepted the connection, but when it tried to handle it, more than 10 seconds later, it was too late and the file wasn't there any more. So, if I understood, clamd accept connections while reloading the database, but handle them later. Am I wrong ? _______________________________________________ Help us build a comprehensive ClamAV guide: visit http://wiki.clamav.net http://www.clamav.net/support/ml
