Hi, SVN or CVS work very well for this; I personally use SVN. Version control admin directories will not interfere with Nagios parsing configs from directories as it looks for files that end in .cfg (as you pointed out in your post).
Terrific way to keep a hot backup of your configs off site and to allow multiple configuration editors to work on files concurrently; you could even tie in a nice project management web interface like Trac for SVN and have a central place for people to easily see what changed when via the web as well as managing requests for changes to Nagios (new service / host monitoring requests etc) using the trouble ticketing features of a system like Trac ... and then their monitoring requests can be tied back to change sets by using the Milestone features of Trac. Lots of nice possibilities, especially for environments with multiple editors and multiple users who can request service and host monitoring changes. - Max ------------------------------------------------------------------------- This SF.net email is sponsored by the 2008 JavaOne(SM) Conference Don't miss this year's exciting event. There's still time to save $100. Use priority code J8TL2D2. http://ad.doubleclick.net/clk;198757673;13503038;p?http://java.sun.com/javaone _______________________________________________ Nagios-users mailing list Nagios-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/nagios-users ::: Please include Nagios version, plugin version (-v) and OS when reporting any issue. ::: Messages without supporting info will risk being sent to /dev/null
