On Tue, 21 Sep 2010 13:12:39 -0400 Nathan Gibbs
nat...@cmpublishers.com wrote:
It appears that if an OnErrorExecute Event can fire, that an OnOutdatedExecute
Event won't fire even if it could.
For instance a Clamav Installation with
Engine0.96.2
DB Version11991
1. I cycle the freshclam service.
2. It tries to update the DB's and fails.
3. I get the OnErrorExecute Message.
4. I don't get the OnOutdatedExecute Message.
Both apply, why do I just get one?
However, if
1. I cycle the freshclam service.
2. It tries to update the DB's and succeeds.
3. I'll get the OnUpdateExecute Message and the OnOutdatedExecute Message.
As I'd expect to.
Is this a bug or a feature?
This is by design. When the db update process terminates with an error,
freshclam only calls OnErrorExecute. There's no guarantee the TXT record
was parsed (some problems could occur before even making the DNS query),
therefore to be consistent OnOutdatedExecute never gets called on error
conditions.
--
oo. Tomasz Kojm tk...@clamav.net
(\/)\. http://www.ClamAV.net/gpg/tkojm.gpg
\..._ 0DCA5A08407D5288279DB43454822DC8985A444B
//\ /\ Wed Sep 22 11:53:36 CEST 2010
___
Help us build a comprehensive ClamAV guide: visit http://wiki.clamav.net
http://www.clamav.net/support/ml
