Tomasz Kojm wrote: > It should be triggered on both version and f-level warnings (but only > once even if both of them are reported).
Hello Tomasz. That's exactly what I was interested in discussing. Here are a set of assumptions - 1. the current software will always support the current database. _Current_ being what is reported by the DNS query - not what is installed. 2. an increase in functionality in the database will always be accompanied by an increase of the software version/release. 3. not necessarily vice-versa, although it would be reasonable to expect it. So, a situation where the new database requires flevel 5, but the software only supports flevel 4, would be impossible unless a software-level warning had already been issued? (according to the current code-sequence). Am I right or am I just babbling? > Another thing that must be addressed in your patch is the execution point - > running a command > before a database update is not safe (move it at the end of > downloadmanager()). OK, I'll bear that in mind. -- /Per Jessen, Zürich _______________________________________________ http://lurker.clamav.net/list/clamav-devel.html
