Török Edwin wrote: > On 2009-02-28 22:25, Dennis Peterson wrote: >> This is important because I have a clamd farm and now with the 0.95rc1 >> release I >> have a mismatch. And since communications has changed I have to build a >> one-to-one relationship with the client and the daemon and I'm not real >> happy >> with that solution. A version discovery option from a remote system is a >> good idea. > > Hi Dennis, > > This is already possible with the clamdtop in SVN (I fixed it, so that > it can connect to 0.94.2 clamd too). > See the discussion here: > https://wwws.clamav.net/bugzilla/show_bug.cgi?id=1437#c6 > > Best regards, > --Edwin
clamdtop is a cute program but interactive. It does not provide a programmatic way to roll out upgrades in a methodical way. It may not even be installed on the headless systems that need the information interactively. Changing the communication protocol impacts all the client software. In order to do load and regression testing it is necessary to put new code in a limited production environment where it is a peer system, and the legacy software has to know about the quirks introduced in the new product. What Jose is suggesting is a good way for client software to test for this going forward. It won't help the existing installations as it's too late for that, but the next releases and beyond will benefit. Summary: Cute interactive visual tools developed in and for a Linux environment are no solution for API standards and where programmatic means of identifying version characteristics are preferred. dp _______________________________________________ Help us build a comprehensive ClamAV guide: visit http://wiki.clamav.net http://www.clamav.net/support/ml
