check_ping packet loss issue, Andreas Ericsson's replacement

[Andreas Ericsson]

Noah Leaman wrote:
> I am trying to solve the issue of the check_ping plugin generally 
> reporting packet loss when that doesn't seem to really be the case. it 
> seems this is a common problem. I am using nagios 1.3 with the 
> changed-ash patch and plugins 1.3.1.
> 
> 1) Am I right in thinking that the check_ping "bogus" packet loss issue 
> is a valid and somewhat common (perhaps inly certain environments)?
> 
> 2) I am also using Mac OS X (Panther), and it seems the check_fping 
> didn't compile or install. Not 100% sure why. i just compiled Andreas 
> Ericsson's replacement but got these errors when compiling:
> 
> $ make
> rm -f *.o a.out core check_fping
> gcc -O2 -funroll-loops -fomit-frame-pointer -g -ggdb -W -Wunused -Wall 
> -Wstrict-prototypes   -c -o check_fping.o check_fping.c
> check_fping.c: In function `main':
> check_fping.c:406: warning: unsigned int format, long unsigned int arg 
> (arg 4)
> gcc   check_fping.o   -o check_fping
> 
> Am I safe still using it? Seems to work with what I've tested. Or is 
> there any changes I could make to have it compile without any warnings?
> 
Yes, you're safe. It's just a printf() format line with an error 
message, and it does in no way affect logic or normal operation (it 
doesn't affect the error message either, afaik, but I'll have it fixed 
anyways).

Btw. Nice to see it in use. :-)

-- 
Mvh
Andreas Ericsson
OP5 AB
+46 (0)733 709032
andreas.ericsson at op5.se


-------------------------------------------------------
This SF.Net email is sponsored by: SourceForge.net Broadband
Sign-up now for SourceForge Broadband and get the fastest
6.0/768 connection for only $19.95/mo for the first 3 months!
http://ads.osdn.com/?ad_id=2562&alloc_id=6184&op=click
_______________________________________________
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