Stephen Gran said: > On Thu, Aug 18, 2005 at 04:00:19PM +0200, Marc Haber said: >> Hi, >> >> the clamd docs say quite clearly that it is necessary to either send >> the RELOAD command to the daemon or to send SIGUSR2 to the daemon to >> have it reload the database. >> >> However, the VERSION command and clamdscan -V report the new database >> version immediately after putting the new databases in place. > > OK, I have been thinking about this a little more, and it looks to me > like the simplest thing may be to add an element to the cl_node root > struct containing version information.
If I were king and could set priorities and someone has dev cycles to burn I'm much rather see a control channel added to clamd that listens on a separate port from the data port (3311, 'fristance). This new control port would be a tcp socket only and could be bound to the loopback interface or to a network interface, and it would allow queries from tools such as Big Brother, Big Sister, Auntie Em, or Network Node Manager, what ever. This allows using the more efficient Unix socket for the data passing while allowing remote access to the daemon for testing, querying, forcing reloads, etc. And while you're in there, who ever "you" might be, do it to freshclam's daemon mode, too. dp _______________________________________________ http://lurker.clamav.net/list/clamav-users.html
