[Xymon] batch configuration of critical systems?

[Richard L. Hamilton]

Thanks.  Since the man page for the file purposely does not document the format, how might one best determine that?  Creating a bunch of entries with the web interface _might_ do, if one carefully exercised each feature; or I suppose there’s the option of digging through the source.  Any other ideas?


On Oct 15, 2014, at 10:51 PM, Jeremy Laidman <jlaidman at rebel-it.com.au> wrote:

> On 16 October 2014 11:58, Richard Hamilton <rlhamil2 at gmail.com> wrote:
> Is there a recommended/supported mechanism to configure (and as needed, update or replace the configuration) of critical systems from the command line?
> 
> I doubt it.  There's only one binary that updates the critical configuration file, and that's criticaleditor.cgi.
> 
> You might be able to cobble together a script that calls criticaleditor.cgi with the required parameters/environment to simulate a web browser. But it seems a lot of trouble, when you can just update the file.
> 
> As far as I can tell, there's no locking in the web interface, so if two updates happen at around the same time, the second one wins, and the changes in the first save will be lost.  So I don't think you can make it much worse by implementing an extra interface to the file, but if you wanted to avoid concurrency problems like this, you could disable the CGI, and also include some kind of locking code in your own script.
> 
> J
> 

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.xymon.com/pipermail/xymon/attachments/20141016/6a1bfb75/attachment.html>