This is a good point.

On the other hand, the current default, UDP, typically returns false even when pinging the local host (127.0.0.1). This, by itself, has caused so much confusion that there are posts all over the 'net asking, basically, "Why doesn't Net::Ping work?" My general idea for fixing this problem is to always use the most accurate ping available on a given system. If people can't be bothered to read the POD, I guess I consider that their own problem. On the other hand, I think the major problem here is that the current POD gives no explanation of why some types of ping are incredibly inaccurate.

I suppose we could default to ICMP, which would actually make most (non-root) people read through the POD before playing with the module.

In reply to Re: Re: RFC on Net::Ping by Falkkin
in thread RFC on Net::Ping by Falkkin

Title:
Use:  <p> text here (a paragraph) </p>
and:  <code> code here </code>
to format your post, it's "PerlMonks-approved HTML":


  • Posts are HTML formatted. Put <p> </p> tags around your paragraphs. Put <code> </code> tags around your code and data!
  • Titles consisting of a single word are discouraged, and in most cases are disallowed outright.
  • Read Where should I post X? if you're not absolutely sure you're posting in the right place.
  • Please read these before you post! —
  • Posts may use any of the Perl Monks Approved HTML tags:
    a, abbr, b, big, blockquote, br, caption, center, col, colgroup, dd, del, details, div, dl, dt, em, font, h1, h2, h3, h4, h5, h6, hr, i, ins, li, ol, p, pre, readmore, small, span, spoiler, strike, strong, sub, summary, sup, table, tbody, td, tfoot, th, thead, tr, tt, u, ul, wbr
  • You may need to use entities for some characters, as follows. (Exception: Within code tags, you can put the characters literally.)
            For:     Use:
    & &amp;
    < &lt;
    > &gt;
    [ &#91;
    ] &#93;
  • Link using PerlMonks shortcuts! What shortcuts can I use for linking?
  • See Writeup Formatting Tips and other pages linked from there for more info.