Bug 9025 - Ping changes
Summary: Ping changes
Alias: None
Product: Red Hat Linux
Classification: Retired
Component: netkit-base   
(Show other bugs)
Version: 6.1
Hardware: All
OS: Linux
Target Milestone: ---
Assignee: Jeff Johnson
QA Contact:
Depends On:
TreeView+ depends on / blocked
Reported: 2000-01-31 19:41 UTC by John W Eckhart
Modified: 2008-05-01 15:37 UTC (History)
0 users

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Last Closed: 2000-01-31 19:59:41 UTC
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Attachments (Terms of Use)

Description John W Eckhart 2000-01-31 19:41:55 UTC
Under the new version of redhat I have noticed that the ping component
appears to be updated. However, as part of the update, if the -c count
flag is used ping will not stop until "count" pings have been returned.
The documentation reports that if ping goes "count" counts without a
single return it will also abort. However, when testing my network, if a
server is down and ping cannot reach it, it will continue to ping until
manually stopped, no matter what "count" is specified. I am running ping
inside another program that automatically checks the network status every
fifteen minutes so there is no way anyone can watch that program to make
sure that it completes every fifteen minutes. Is there a fix for the ping
command to abort it if no response is recieved after "count" tries?

Comment 1 Jeff Johnson 2000-01-31 19:59:59 UTC
Red Hat 6.x does not use the ping from netkit-base, but rather a version
from Alexei Kuznetsoff that is more appropriate for modern linux kernels.

That version has changed the semantics of "-c N" to wait for N received
packets, rather than N sent packets. This change is necessary to acquire
rtt with constant statistical accuracy, the other use of the "-c N" option.

Use the new "-w secs" flag if you want a deterministic exit for hosts that
may not be reachable. Or, recompile the netkit-base (now called "inetd") with
the netkit ping.

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