[check_postgres] [commit] Two cool new checks: new_version_cp and new_version_pg to check if you

[Greg Sabino Mullane]

Good point about the versions.rss file, I forgot about that one. Using the ftp
is not a great idea, as pointed out.

>> Critical if lastest release older than X days for example.

I'm not too big on this. Does it really matter how old it is? Out of date is out
of date. I originally was going to just throw a critical for all mismatches, but
changed to a warning at the last moment.

> Hmm... this gives me an idea... possibly we (webteam) could modify the rss 
> feed to include whether a release includes security fixes, so that we 
> (check_postgres) could adjust nagios check based on that information. 

Interesting - but has there ever really been a non-vital point update? If it's
not a security fix, it's usually something that might compromise your data,
which is just as important. I'd say even more so, actually, as most of the
recent 'security fixes' tend to be "problems that could be caused by untrusted
local users" which is not a concern for many places.

Anyway, random thoughts, I'll try and make the version.rss changes later today.

-- 
Greg Sabino Mullane greg at endpoint.com
End Point Corporation
PGP Key: 0x14964AC8

-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 226 bytes
Desc: OpenPGP digital signature
Url : https://mail.endcrypt.com/pipermail/check_postgres/attachments/20090408/b1d060d1/attachment.bin