change management or source control for Nagios configs?

[Frost, Mark {PBG}]

I'm wondering what most people out there use for change management of
Nagios config files.  I had been using BZR (bazaar-ng) for a while, but
when I refreshed my servers it was a bit of a pain and haven't put it
there yet.  I've tried to read about other ways to do this (RCS, SVN,
etc), but they all seem so strongly oriented towards source-code
projects that it's kind of confusing to run them with just config files.

Some of these methods are complicated by the fact that they want to make
their archive directory inside Nagios' directory structure.  This gets
kind of weird as I use nagios.cfg directives to tell it to recursively
read directories rather than just specifically named files.  BZR worked
OK in this regard as it's dir was ".bzr" and was never picked up by
Nagios.

Ultimately, I'm trying to provide myself with the ability to track
changes and potentially roll them back.  Is anyone else out there using
some wonderful solution to this?

Thanks

Mark

-------------------------------------------------------------------------
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 at 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