Bug 9049 - Ping command (again)
Ping command (again)
Product: Red Hat Linux
Classification: Retired
Component: netkit-base (Show other bugs)
All Linux
high Severity medium
: ---
: ---
Assigned To: Jeff Johnson
Depends On:
  Show dependency treegraph
Reported: 2000-02-01 16:46 EST by John W Eckhart
Modified: 2008-05-01 11:37 EDT (History)
0 users

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Last Closed: 2000-03-05 12:41:16 EST
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Attachments (Terms of Use)

  None (edit)
Description John W Eckhart 2000-02-01 16:46:25 EST
When attempting to limit the ping command to a specific time period using
the -w option I am faced with a similar problem as when using the -c
option. The -w option will only stop the ping command after wait seconds if
it recieves a response from the computer being pinged. Otherwise it will
continue to ping that computer indefinately. Is there a fix to limit the
ping command if it does not receive a response from a server such that it
can be automated? The -w command should work regardless of whether the
other computer responds or not.
Comment 1 Jeff Johnson 2000-03-05 12:41:59 EST
Use both -c <npackets> and -w <nsecs>, this works for me using the ping
in iputils-20000120-1 from Raw Hide.

Note You need to log in before you can comment on or make changes to this bug.