Re^3: RRD-Ping getting values on right interval

If you look at the ping report, the RT times (as printed) total 25 miliseconds; at the moment, I'm looking at RTs on the order of 90 milisecs. Either adds up to half a sec pretty fast -- just 6 (+/-) iterations in my case; 20 in yours.

BTW, your script requires mods/workaround beyond my ken for Windoze/AS 5.12...:
Your vendor has not defined POSIX macro WUNTRACED, used at F:\_Perl_\pl_test\940785.pl
at my equivalent of your line 45.

Comment on Re^3: RRD-Ping getting values on right interval

Replies are listed 'Best First'.
Re^4: RRD-Ping getting values on right interval by hello_world (Acolyte) on Nov 30, 2011 at 13:09 UTC
You can substitute that with normal waitpid.That should work i guess.I didnt quite get how did you arrive at the value of '20'. Thanks	[reply]
Re^5: RRD-Ping getting values on right interval by ww (Archbishop) on Nov 30, 2011 at 14:04 UTC
20 iterations * 25 milisec/iteration = 500 milisecs or 0.5 seconds Actually, the sum of your RTs is 23 milisec, but that's close enough for this explanation, as is the WAG that `-w 15` will net (roughly) a thruput of 20 iterations.	[reply] [d/l]