I'm gathering that said data ends up in $XYMONCLIENTHOME/tmp/logfetch.$MACHINEDOTS.cfg.
Would it hurt anything to put (on the server) data in addition to the lines defined in the man page? Would it make it back to the above file?
And if so, can a naming convention be recommended for user-defined lines that should avoid conflict with any future official lines? (maybe names that begin with site_ or something like that?)
And if that's not all crazy...it would be cool if the library module to fetch the client-local.cfg for a host could check the timestamp on the file, and if changed, reload it (freeing all the old data structures first, so as not to leak memory, of course!)
That way, without restarting the server, one could replace the client-local.cfg file on the server and have client log, file, and extension script behavior altered accordingly.
Having used Big Brother for many years, the ability of Xymon to pass updates and _some_ client control information to the client, without one inventing one's own backchannel (using ssh or whatever), sounds like it could make life _much_ simpler in terms of centralizing the control of clients and server alike. So naturally I want to take that to its logical extreme. :-) But so far, I haven't read enough of the code to really have a good handle on just what might be possible, let alone normal enough not to be too fragile.