>
> --- In [email protected], "mockey_a" <mockey@> wrote:
> > I don't know all the possibilities but maybe another parameter is
> not
> > relly necessary. IMO only a ping where packets are received should
> be
> > considered as "successful", everything else is "unsuccessful", isn't
> > it?
It's a possible definition of failure, but I don't want to change
observable behaviour for existing scripts if it's not necessary.
If I add another param, it will be optional, defaulting to
current behaviour.
> Hmm, not quite. "host not reachable" is also possible. Pinging from
> the DOS-console counts that as received packet. net_packets_recvd
> returns 0 then, though. Maybe you just leave it as it is and I use a
> callback-function analyzing net_packets_recvd.
I've got the code mostly in place for extra param, so will probably
issue it.
I'll extend docs to suggest callback-function analyzing net_packets_recvd.
> BTW: I just saw that the extended net-vars for pinging are just set
> when calling net.get_ping_result(). Might be useful when they are set
> together with the callback-function of net.ping_threaded as well...
No, because it's a lot of extra vars, and many users might not want
them. The idea is you call net.get_ping_result() when you need it,
and a common place to call it might be your success callback code.
The raw material for calculating extended results is always there
after a ping; you just need to do the net.get_ping_result() to get them.
Attention: PowerPro's Web site has moved: http://www.ppro.org
SPONSORED LINKS
| Computer monitoring software | Power pro | Computer and internet software |
| Free computer monitoring software |
YAHOO! GROUPS LINKS
- Visit your group "power-pro" on the web.
- To unsubscribe from this group, send an email to:
[EMAIL PROTECTED]
- Your use of Yahoo! Groups is subject to the Yahoo! Terms of Service.
