From: Glen Holcomb <damnbigman@...>
Date: 2007-03-17T03:58:58+09:00
Subject: Re: The philosophy of failed pings

------=_Part_89337_5739774.1174071530659
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Content-Disposition: inline

100% loss sounds like an absolute failure to me, at least with a vanilla "Is
it up?" situation.

On 3/16/07, Daniel Berger <djberg96@gmail.com> wrote:
>
> Hi all,
>
> I need some advice. I recently received a bug report for
> Net::Ping::External class (part of
> the net-ping package) where the user was getting false positives.
>
> In his case he was pinging some bogus loopback address. The ping
> command did not raise any error or warning, but it did have 100%
> packet failure.
>
> So, my question is, should I look for "100% packet loss" in the output
> and, if found, consider that a failed ping no matter what? I know I
> could make it configurable, but even if I go that route, I'd like to
> know what the default behavior should be.
>
> It wouldn't be hard to implement, but I thought I would ask since I
> think this package is fairly popular now I think and I want to get
> feedback before I start breaking things.
>
> Thanks,
>
> Dan
>
>
>


-- 
"Hey brother christian with your high and mighty errand, Your actions speak
so loud, I can't hear a word you're saying."

-Greg Graffin (Bad Religion)

------=_Part_89337_5739774.1174071530659--