Bug 4149 - ping is now broken in 6.0 i386
ping is now broken in 6.0 i386
Status: CLOSED DUPLICATE of bug 4082
Product: Red Hat Linux
Classification: Retired
Component: netkit-base (Show other bugs)
i386 Linux
medium Severity medium
: ---
: ---
Assigned To: David Lawrence
Depends On:
  Show dependency treegraph
Reported: 1999-07-21 17:24 EDT by jimbrown
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: 1999-07-23 04:11:54 EDT
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 jimbrown 1999-07-21 17:24:33 EDT
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 :

jab-linux.isd.ustra.abb.com:/jbrown/linux/errata$ ping
PING ( from : 56
data bytes
>From jab-linux.isd.ustra.abb.com (
Destination Host
>From jab-linux.isd.ustra.abb.com (
Destination Host
>From jab-linux.isd.ustra.abb.com (
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
Comment 1 David Lawrence 1999-07-22 11:10:59 EDT
I could not get this update to fail on a test lab machine running
standard 6.0 with updates.
Comment 2 Jeff Johnson 1999-07-23 04:11:59 EDT
*** This bug has been marked as a duplicate of 4082 ***

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