Note: This is a beta release of Red Hat Bugzilla 5.0. The data contained within is a snapshot of the live data so any changes you make will not be reflected in the production Bugzilla. Also email is disabled so feel free to test any aspect of the site that you want. File any problems you find or give feedback here.
Bug 3959 - Ping "-c" now hangs on downed servers.
Summary: Ping "-c" now hangs on downed servers.
Alias: None
Product: Red Hat Linux
Classification: Retired
Component: netkit-base
Version: 6.0
Hardware: All
OS: Linux
Target Milestone: ---
Assignee: Jeff Johnson
QA Contact:
: 4082 (view as bug list)
Depends On:
TreeView+ depends on / blocked
Reported: 1999-07-09 07:49 UTC by jafo-redhat
Modified: 2008-05-01 15:37 UTC (History)
1 user (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Last Closed: 1999-08-09 20:14:14 UTC

Attachments (Terms of Use)

Description jafo-redhat 1999-07-09 07:49:13 UTC
With netkit-base-0.10-31, code was removed which caused
termination when the "-c <N>" packets were sent.  This
causes problems if you are using ping from a script to
monitor a downed host.

Also, the documentation includes the phrasing "Stop after
sending (and receiving) [...]".  If the intention is that
(unlike other systems) it only count *RECEIVED* packets,
why is that in parenthesis.

The patch I will be submitting shortly changes the man page
and causes the old behavior of terminating after N packets
are sent (and responses waited for).

EFFECT: Without this fix, netsaint (and other monitoring
software I'm sure) fills up your process table with pings.


Comment 1 Jeff Johnson 1999-07-23 08:20:59 UTC
*** Bug 4082 has been marked as a duplicate of this bug. ***

On the alpha, netkit-base-0.10-29 had the unaligned trap
bug, but after installing netkit-base-0.10-31 (which fixed
the unaligned trap) ping -c does not work properly.

Specifically, "ping -c x unreachable-host" causes ping to
start a stream of pings (as seen by tcpdump) that does not
stop after "x" pings.  Pinging a host that is reachable with
the -c option works properly.

In this case, I use ping -c to bring up a demand ppp link so
I have reverted to the 0.10-29 kit shipped with 6.0 Alpha.


------- Additional Comments From  07/22/99 11:33 -------
I was able to replicate this problem on an alpha and intel machine in
our test lab with this update. I tried to ping and which are set up to reject ping requests so therefore I
get the unreachable errors. It seems the -c <some num> option is
ignored when used and a host is unreachable. This is being assigned to
a developer for further review.

------- Additional Comments From  07/23/99 04:09 -------

*** Bug 4169 has been marked as a duplicate of this bug. ***

Here is the transcript of my session notice that I installed
the original rpm ran my test then ran the new rpm and it

Transcript follows:

[root@jab-linux RPMS]# rpm -U --oldpackage
[root@jab-linux RPMS]# ls -l /bin/ping
-rwsr-xr-x   1 root     root        14804 Apr  7 17:21
[root@jab-linux RPMS]# ping -c 1
PING ( 56 data bytes

--- ping statistics ---
1 packets transmitted, 0 packets received, 100% packet loss
[root@jab-linux RPMS]# cd /jbrown/linux/errata
[root@jab-linux errata]# rpm -U netkit-base-0.10-31.i386.rpm
[root@jab-linux errata]# ls -l /biin/ping
ls: /biin/ping: No such file or directory
[root@jab-linux errata]# ls -l /bin/ping
-rwsr-xr-x   1 root     root        17652 Jul  6 09:33
[root@jab-linux errata]# ping -c 1
PING ( from : 56
data bytes
From (
Destination Host Unreachable
From (
Destination Host Unreachable

--- ping statistics ---
2 packets transmitted, 0 packets received, +2 errors, 100%
packet loss
[root@jab-linux errata]#

------- Additional Comments From  07/23/99 04:11 -------

*** Bug 4149 has been marked as a duplicate of this bug. ***

I beleive there is a problem with
netkit-base-0.10-31.is86.rpm I have a
script that pings hosts and ever since I applied the errata
ping now
fails with this error message :$ ping
PING ( from : 56
data bytes
>From (
Destination Host
>From (
Destination Host
>From (
Destination Host

There is no host the at that address and I should not be
getting this
error. I have an original 6.0 install which has a different
date and
size from the original. The dates on the original install

14804 Apr 7 ping

and the new one is:

17652 Jul 6 ping

 This effectivly breaks ping. Which is vital to my script.
Meanwhile I
have moved the older version onto this computer and I have
changed my
script to refernece the old version of ping. If someone
could please
look into why this is happening. Oh the platform is Intel.

                                            Jim Brown

------- Additional Comments From  07/22/99 11:10 -------
I could not get this update to fail on a test lab machine running
standard 6.0 with updates.

Comment 2 Jeff Johnson 1999-08-09 20:14:59 UTC
Fixed in netkit-base-0.10-33.

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