[Nagiosplug-devel] Best Way to Monitor Cruisecontrol

[Robert Pearse]

I don't want to change the Cruisecontrol installation. There's already
too much involved in configuring it, as it is.

Maybe I should have asked for the best way to monitor and remote file.

Robert

> -----Original Message-----
> From: Jason Martin [mailto:jhmartin at toger.us]
> Sent: Wednesday, February 18, 2004 5:06 PM
> To: Robert Pearse
> Cc: nagiosplug-devel at lists.sourceforge.net
> Subject: Re: [Nagiosplug-devel] Best Way to Monitor Cruisecontrol
> 
> -----BEGIN PGP SIGNED MESSAGE-----
> Hash: SHA1
> 
> If is is a continous process then you could have the cruisecontroll
> program send a passive check every time it completes a cycle and use
> freshness checking to verify that you've received it in time.
> 
> - -Jason Martin
> 
> On Wed, 18 Feb 2004,
> Robert Pearse wrote:
> 
> > For those of you that are unfamiliar with Cruisecontrol, it's
another SF
> > project that constantly builds code in a loop. Every so often, as
> > configured, it will start a build if it has seen a CVS commit.
> >
> >
> >
> > I'm trying to monitor the Cruisecontrol process on a remote server
using
> > Nagios. I think the easiest way to do that is to monitor
> > cruisecontrol.log and see if the file is changing every half hour.
If
> > not, then it's stuck.
> >
> >
> >
> > What's the best way to monitor a file for changes on a remote
server?
> >
> >
> >
> > Thanks,
> >
> >
> >
> > Robert
> >
> >
> -----BEGIN PGP SIGNATURE-----
> Version: GnuPG v1.3.3 (GNU/Linux)
> Comment: pgpenvelope 2.10.2 - http://pgpenvelope.sourceforge.net/
> 
> iD8DBQFAM/AAl2ODWuqVSBMRAnNNAJ9KpQZIAxxXp4W8wlyx6JQes3TicwCeJljc
> jsVEuDR0zpC6PXBojV4iTSs=
> =wDZn
> -----END PGP SIGNATURE-----