You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
When doing a --reverse check with custom_query and using both warning and critical values, the result is always OK.
This is caused by the sub validate_range () which returns no values back to custom_query.
I fixed it with the following lines:
2187 if (length $warning and length $critical and $warning > $critical) { {
2188 # Original
2189 #return if $opt{reverse};
2190 # Option 1, following checks won't get executed
2191 #return ($warning,$critical) if $opt{reverse};
2192 # Option 2, break out of the if statement, needs another { }
2193 last if $opt{reverse};
2194 ndie msg('range-warnbig');
2195 } }
As I'm not a programmer, could you please review and if ok, include it in the next release.
Cheers
Tobias
The text was updated successfully, but these errors were encountered:
When doing a --reverse check with custom_query and using both warning and critical values, the result is always OK.
This is caused by the sub validate_range () which returns no values back to custom_query.
I fixed it with the following lines:
2187 if (length $warning and length $critical and $warning > $critical) { {
2188 # Original
2189 #return if $opt{reverse};
2190 # Option 1, following checks won't get executed
2191 #return ($warning,$critical) if $opt{reverse};
2192 # Option 2, break out of the if statement, needs another { }
2193 last if $opt{reverse};
2194 ndie msg('range-warnbig');
2195 } }
As I'm not a programmer, could you please review and if ok, include it in the next release.
Cheers
Tobias
The text was updated successfully, but these errors were encountered: