Jose-Marcio Martins da Cruz wrote: > Török Edwin wrote: >> On 2009-02-28 12:18, Jose-Marcio Martins da Cruz wrote: >>> I see. Removing a '\n' when it's just before the '\0' may not be better >>> but doesn't harm. I'm wrong ? >>> >> As I said, that is a problem if the filename ends with \n, if I remove >> the \n it will no longer find the file. > > ... > >> Use nCOMMANDS, those work with both old, and new clamd. > > It could be interesting to have a command which answers correctly, with > a hint about the version or options available, no matter how it ends : > with a '\n' or a '\0'. It could be VERSION, or PING (if you add some > data after PONG), or a new command. This way, the clamd client could > adapt itself to clamd behaviour, instead of guessing or using an > obsolete command. > > Either way, nCOMMANDS still remain interesting when using a telnet > client for, e.g., debug purposes. > > Regards, > > JM > >
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. dp _______________________________________________ Help us build a comprehensive ClamAV guide: visit http://wiki.clamav.net http://www.clamav.net/support/ml
