From: Francis Cianfrocca <garbagecat10@...>
Date: 2007-03-17T21:01:18+09:00
Subject: Re: The philosophy of failed pings

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

On 3/17/07, Daniel Berger <djberg96@gmail.com> wrote:
>
> Yes. In all of my past experiences when that happened there would be
> some additional output sent to stderr, or something sent to stdout
> that warned you something was wrong, and so my code relied on that. In
> this particular case there was no warning or error.
>
> > I don't think #ping(host) should return true unless there has
> > actually been a packet returned from the targeted host.
> >
> > Not sure if that answers your question though.
>
> Yeah, the more I think about it, the more I'm leaning in that
> direction.



This is probably silly, but ping isn't that hard. Couldn't you just
implement it with a raw socket? (Or supply both flavors, the ICMP and the
UDP.) Then you'd have complete control over the outcome.

------=_Part_74441_15736973.1174132876991--