I should write a patch to make it configurable...
That'd be nice =)
Ehrm, I just looked in the code of nrpe 2.12...
This function is already in (-u). I still had 2.5.1 (Debian Etch).
This really hurts... :-)
Cheers
Klaus
--
BOFH excuse #75:
There isn't any problem
Hi,
I have a problem with unstable lines and/or machines under stress.
Sometimes they just don't reply on nrpe, but are still working, so I get a
lot of false alarms. Is it possible, to tell check_nrpe to exit with a
warning instead of critical?
Cheers
Klaus
--
BOFH excuse #401:
On Thu, Feb 26, 2009 at 5:21 AM, Klaus Umbach
treibh...@sozial-inkompetent.de wrote:
Hi,
I have a problem with unstable lines and/or machines under stress.
Sometimes they just don't reply on nrpe, but are still working, so I get a
lot of false alarms. Is it possible, to tell check_nrpe to
On 26/02/09 12:06, Lee Azzarello wrote:
On Thu, Feb 26, 2009 at 5:21 AM, Klaus Umbach
treibh...@sozial-inkompetent.de wrote:
Hi,
I have a problem with unstable lines and/or machines under stress.
Sometimes they just don't reply on nrpe, but are still working, so I get a
lot of false
On Feb 26, 2009, at 1:02 PM, Klaus Umbach wrote:
Most of time I know the cause, but it is not solvable in a cheap
way :-)
The relevant services are still working, but if the monitored values
pass
the thresholds, I want to know it, not if connection fails.
Edit check_nrpe.c; look for
On 26/02/09 13:18, Marc Powell wrote:
change STATE_CRITICAL to whatever state you think it should be and
recompile.
Yes, that solution is an option, too, but I was hoping to find something
without recompiling :-)
I should write a patch to make it configurable...
Cheers
Klaus
--
On Feb 26, 2009, at 2:13 PM, Klaus Umbach wrote:
On 26/02/09 13:18, Marc Powell wrote:
change STATE_CRITICAL to whatever state you think it should be and
recompile.
Yes, that solution is an option, too, but I was hoping to find
something
without recompiling :-)
The negate plugin is
