Re: [Nagios-users] change control on Nagios / Cacti servers

if you cannot rely on the others using version control systems, then you might consider tripwire. Be careful though, you might end up getting a LOT of "spam" mails.

--
Esben


Rogelio Bastardo wrote:

> I'm looking for some sort of change control  solution. On several 
> Cacti/Nagios servers, I would like to take a snapshot of what I did, 
> back it up, and if something changes, run something that shows me what 
> files / permissions were changed since I last worked on the server.
>  
> If it were just me, then I would just make copies of the files.  But 
> since there are other people in there doing all sorts of weird 
> configs, I want to make sure that I document what they did since I 
> last logged in.
>  
> Any suggestions would be greatly appreciated.
> ------------------------------------------------------------------------
>
> -------------------------------------------------------------------------
> This SF.net email is sponsored by: Microsoft
> Defy all challenges. Microsoft(R) Visual Studio 2005.
> http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/
> ------------------------------------------------------------------------
>
> _______________________________________________
> 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



-------------------------------------------------------------------------
This SF.net email is sponsored by: Microsoft
Defy all challenges. Microsoft(R) Visual Studio 2005.
http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/
_______________________________________________
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