On 03/29/2012 08:00 AM, Thomas Guyot-Sionnest wrote:
> -----BEGIN PGP SIGNED MESSAGE-----
> Hash: SHA1
>
> On 12-03-28 08:52 AM, SCHAER Frederic wrote:
>> Hi,
>>
>> when the patch is not enough (this happened to me), you can transfer about 300KB of text data using both the patch + bzip2 +
>> uuencode on the nrpe side, and bunzip + uudecode decoder on the nagios side...
>> base64/uu encoding increases the size, but nrpe is not happy with binary data.
>>
>> Bzip+uuencoding was the best solution I could find - and that was available on all my managed machines, thus not requiring to
>> deploy more packages.
>> I havent't tried this method without the patch : it might help transferring a bit more data than 4Kbytes (or 8K ?) - or not...
>
> 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?
--
Andreas Ericsson [email protected]
OP5 AB www.op5.se
Tel: +46 8-230225 Fax: +46 8-230231
Considering the successes of the wars on alcohol, poverty, drugs and
terror, I think we should give some serious thought to declaring war
on peace.
This post was automatically imported from historical nagios-devel mailing list archives
Original poster: [email protected]