On Apr 15, 2008, at 6:44 AM, Tom Throckmorton wrote: > On Apr 10 23:05, Max wrote: >> 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.
I also use SVN + Trac. I wrote an script to sync my config files - on multiple hosts and not just for nagios - up to the svn server via cron. It works really well and most of the time I don't need the files to be uploaded immediately after I make changes, so I do it once a day and always have the rev history. Works really well and I use it also for /etc dirs and other config directories as well. Rob ------------------------------------------------------------------------- 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