On 05/22/2010 07:22 PM, Dennis Peterson wrote: > On 5/22/10 1:12 AM, Török Edwin wrote: >> On 05/22/2010 08:34 AM, Dennis Peterson wrote: >>> Has the team explored the notion of checking MD5 hashes of signature >>> files before deciding to reload them? >> >> This might be useful if partial reloads would be supported, but see >> below. >> >> clamd checks the timestamp on the DB, and reloads it if it has changed, >> or if freshclam/clamdscan --reload explicitly tells it to reload. >> >> Is there a situation where the timestamp changes but the DB stays the >> same? > > What I see is that if I issue a RELOAD to the clamd socket it will > reload all the signature files if they've changed or not. I'd prefer it > reload only the files it has not already seen. If I run the RELOAD > command back to back the second time should scan the time stamps and > quit, but in fact it reloads everything again. > > Perhaps a refresh rather than a reload is what I'm after. I'd just > prefer clamd do the least work needed to be up to date. My understanding > is this is how the internal self-check works.
So you want a reload command equivalent to the internal self-check. Please open an enhancement request on our bugzilla. > Each N seconds clamd looks > for changed files and reloads only them. > > This RELOAD command to the clamd socket is how I tell clamd that 3rd > party signatures have been installed. I could wait for clamd to discover > this, but I'd prefer to let it know. Would be easier if 3rdparty signatures could be downloaded by freshclam, isn't it? Best regards, --Edwin _______________________________________________ Help us build a comprehensive ClamAV guide: visit http://wiki.clamav.net http://www.clamav.net/support/ml
