-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
On 12-03-29 07:09 AM, Andreas Ericsson wrote:
> On 03/29/2012 08:00 AM, Thomas Guyot-Sionnest wrote:
>> -----BEGIN PGP SIGNED MESSAGE-----
>> Hash: SHA1
>>
>> FWIW I approached the problem a different way - I wrote a simple bash
>> script associated with an SSH key that reads nrpe.conf and run the
>> requested command - it doesn't support arguments (yet) and require a
>> recent (regex-enabled) version of bash. On old servers I just compiled a
>> recent bash as "bash3" and used it in the #! line...
>>
>> You can get the script here...
>> http://repo.or.cz/w/thomas_code.git/blo ... _ssh_proxy
>>
>> Then set up a key on the monitoring server, authorized_keys on the
>> remote end (specifying the check_by_ssh_proxy script as forced command),
>> and use the nrpe command names the check_by_ssh command line.
>>
>
> How is that any better than just using check_by_ssh and specifying the
> allowed commands in the config there?
>
Where I used it there was already a maintained nrpe.cfg file, so this
was a drop-in replacement for the nrpe checks using ssh. No need to
define one command per key for instance, and I could use a generic
check_by_ssh command in nagios and pass only the nrpe command name.
Other users are going to update the nrpe.cfg file and my script will
pick up the changes.
I did it to solve the same problem - checks that need to return large
result. However some daemons/clients have been already patched in the
past with no ideas where the source/patches were and I didn't want to
spend time figuring it out or risk breaking anything.
- --
Thomas
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.10 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/
iEYEARECAAYFAk90YgIACgkQ6dZ+Kt5BchZ55wCdEkwrxCCaV0sVSt0HDUnORvig
z+4An1Bc1AMhJy/6zInmTp03vV+uK2BP
=2gOz
-----END PGP SIGNATURE-----
This post was automatically imported from historical nagios-devel mailing list archives
Original poster: [email protected]