[Nagiosplug-help] check_tcp bug in nagios v1.4.11

[Andy Shellam]

Hi Matthias,

While I agree with you about the status code and that this isn't a bug, 
I also agree that all the plugins have a standard format for reporting 
output (i.e. check_name status - output text.)  Something like "TCP 
CRITICAL - Connection refused on port 1234" is more useful and fits the 
"expected standard" of the other plugins, than just "Connection refused".

Andy

Matthias Eble wrote:
> On Thu, 2008-10-23 at 13:00 -0400, Fontanilla, John (Gexpro, consultant)
> wrote:
>   
>> We use check_tcp v.1.4.11 and it appears to still have a bug...
>>     
>
> # check_tcp -H 127.0.0.1 -p 4444; echo $?
> Connection refused
> 2
>
> Why should this be a bug? The plugin returns critical, it simply doesn't
> print the status to stdout. The statustext in the output can be
> considered as noise anyway, since , nagios has appropriate macros, if
> you want a severity string in your notifications, etc.
>
> Matthias
>
>
>
> -------------------------------------------------------------------------
> This SF.Net email is sponsored by the Moblin Your Move Developer's challenge
> Build the coolest Linux based applications with Moblin SDK & win great prizes
> Grand prize is a trip for two to an Open Source event anywhere in the world
> http://moblin-contest.org/redirect.php?banner_id=100&url=/
> _______________________________________________
> Nagiosplug-help mailing list
> Nagiosplug-help at lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/nagiosplug-help
> ::: Please include plugins version (-v) and OS when reporting any issue. 
> ::: Messages without supporting info will risk being sent to /dev/null
>