check_ping and performance data

[Cook, Garry]

nagios-users-admin at lists.sourceforge.net wrote:
> I think the output format is wrong,it needs to be;
> PING OK - Packet loss = 0%, RTA = 0.47 ms |
> packet_loss=0% RTA=0.47ms
> 
> currently it does;
> PING OK - Packet loss = 0%, RTA = 0.47 ms |
> packet_loss=0%;21;31;0;100 RTA=0.47ms;0;0.000000;;

Based on these docs,
http://nagiosplug.sourceforge.net/developer-guidelines.html#AEN185, the
above looks about right. It should be:
'label'=value[UOM];[warn];[crit];[min];[max]

 
> I've tried to modify the output, but not sure what the
> all the %d%% do(some sort of function?), I get
> incorrect results when I modify it...
> 
> 
> --- "Bock, Christian" <Christian.Bock at liz.lsa-net.de>
> wrote:
>> 
>> is it really *that* easy?
>> 
>> I just added the missing information to the output
>> line
>> in check_pinp.c and everything's working great :-)))
>> 
>> chris
>> 
>> 
>> 136c136
>> <               if (display_html == TRUE)
>> ---
>>  >               if (display_html == TRUE) {
>> 139,140c139,140
>> <                       printf (_("PING %s -
>> %sPacket loss = %d%%"), state_text (this_result),
>> warn_text,
>> <
>>    pl);
>> ---
>>  >                       printf (_("PING %s -
>> %sPacket loss = %d%%"),state_text (this_result),
>> warn_text, pl );
>>  >
>> 


Garry W. Cook, CCNA
Network Infrastructure Manager
MACTEC, Inc. - http://www.mactec.com/
303.308.6228 (Office) - 720.220.1862 (Mobile)


-------------------------------------------------------
This SF.Net email is sponsored by The 2004 JavaOne(SM) Conference
Learn from the experts at JavaOne(SM), Sun's Worldwide Java Developer
Conference, June 28 - July 1 at the Moscone Center in San Francisco, CA
REGISTER AND SAVE! http://java.sun.com/javaone/sf Priority Code NWMGYKND
_______________________________________________
Nagios-users mailing list
Nagios-users at lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/nagios-users
::: Please include Nagios version, plugin version (-v) and OS when reporting any issue. 
::: Messages without supporting info will risk being sent to /dev/null