check running on all servers which checks the revision number of the
checkout on that machine by performing a command like "svn info | grep
Revision | awk '{print $2}' ".
If you want to keep the checkout up to date there are a few possibilities:
- create a crontab entry which runs every night and updates the repository
- create a check which compares the output of the above check with the
most recent revision, of which you have a checkout on the Nagios
machine. If it doesn't match, you can return a CRITICAL and create an
event handler which does an "svn update"
- keep them up to date manually
Just my 2 cents
Jeffrey Lensen
System Administrator Hyves
hyves page: http://skyler.hyves.nl
mail/msn: [email protected]
Tobias Mucke wrote:
> Hi,
>
> we are building a RPM package with the standard Nagios plugins, some other plugins from Nagios Exchange and our own plugins. This RPM is rolled out by Cfengine together with nrpe.cfg.
>
> This works quite nice and you need a deployment process / tool for system administration anyway, not only for Nagios plugins.
>
> If you are interested I could post SPEC file and our Cfengine configuration for this task.
>
> Tobias
>
>
> -------------------------------------------------------------------------
> This SF.net email is sponsored by: Splunk Inc.
> Still grepping through log files to find problems? Stop.
> Now Search log events and configuration files using AJAX and a browser.
> Download your FREE copy of Splunk now >> http://get.splunk.com/
> _______________________________________________
> Nagios-devel mailing list
> [email protected]
> https://lists.sourceforge.net/lists/lis ... gios-devel
>
This post was automatically imported from historical nagios-devel mailing list archives
Original poster: [email protected]