Re^3: Net::Ping 2.63 Failing

Should it be trying to actually validate an IP address or just ping it?

By my reading of the Net::Ping::ping() documentation, it should just ping it.

That documentation says, in part:

<quote>
If the hostname cannot be found or there is a problem with the IP number, the success flag returned will be undef. Otherwise, the success flag will be 1 if the host is reachable and 0 if it is not. For most practical purposes, undef and 0 and can be treated as the same case.
</quote>

So, if the ping() function is dying, then it's not behaving as advertised - which makes it a bug.

Cheers,
Rob

Comment on Re^3: Net::Ping 2.63 Failing

Replies are listed 'Best First'.
Re^4: Net::Ping 2.63 Failing by g_speran (Scribe) on Jan 17, 2018 at 04:41 UTC
Agreed, any this is the point that I was trying to make. With that said, whom should I open a bug report with? I have never filed a bug report	[reply]
Re^5: Net::Ping 2.63 Failing by syphilis (Archbishop) on Jan 17, 2018 at 06:04 UTC
With that said, whom should I open a bug report with? Net::Ping is a part of perl core, so you can send your bug report as an email to perlbug@perl.org . AFTERTHOUGHT: I just noticed that perl core currently (perl-5.27.7) has Net-Ping-2.62 - so you probably should check and see what its behaviour is prior to reporting. UPDATE: I finally got around to checking the behaviour with Net-Ping-2.62, and it does have the same buggy behaviour as you reported for 2.63. Most people would file that email by running the perlbug command - as that ensures that all relevant information about your system and perl itself are included in your report Note that there are 2 ways that this bug could be fixed: 1) Restore the previous behaviour of ping(); 2) Alter the documentation of ping() to match the current behaviour. So it's not guaranteed that the behaviour of ping() will be reverted to its earlier form. However, back-compatibility considerations should provide an incentive to go with 1) Cheers, Rob	[reply]