Description: ------------ There's no case for "openbsd" in _createArgList, causing openbsd pings to run indefinitely (needs $count to complete) The "linux" case should work just fine for OpenBSD, and is complete enough to get all args. Test script: --------------- //on an OpenBSD (3.9 in my case) system: <?php $ping = Net_Ping::factory(); if(PEAR::isError($ping)) { echo $ping->getMessage(); } else { $ping->setArgs(array('count' => 2)); var_dump($ping->ping('example.com')); } ?>

We are unable to reproduce the bug as reported. Please provide a simple script (10 lines or less) or a link to an external script that can be used to reproduce the bug. If you can provide the script, feel free to add it to this bug and change the status back to "Open". Thank you for your interest in PEAR. "openbsd" is represented in the code (present in current package release, not just in the CVS repository.) cf line 464 Net_Ping/Ping.php Are you certain your installation returns "openbsd" (literally, no variation whatsoever) when you run: require_once "PEAR.php"; require_once "OS/Guess.php"; $OS_Guess = new OS_Guess; print( $OS_Guess->getSysname() );

> "openbsd" is represented in the code (present in current > package release, not just in the CVS repository.) cf line > 464 Net_Ping/Ping.php That is true for the function "_initArgRelation", the problem is in "_createArgList" starting on line 262. Since there is no "openbsd" case, no arguments are prepared ($retval['pre'] and $retval['post'] in "_createArgList", used as $argList['pre'] and $argList['post'] on line 374) the actual ping command gets run without any arguments, causing it to ping continuously. > Are you certain your installation returns "openbsd" > (literally, no variation whatsoever) when you run: Yes, it does. Thanks for your time and for looking into this!

confirmed

This bug has been fixed in CVS. If this was a documentation problem, the fix will appear on pear.php.net by the end of next Sunday (CET). If this was a problem with the pear.php.net website, the change should be live shortly. Otherwise, the fix will appear in the package's next release. Thank you for the report and for helping us make PEAR better.