Bug 87589 - xinetd uses 98% cpu
xinetd uses 98% cpu
Product: Red Hat Linux
Classification: Retired
Component: xinetd (Show other bugs)
i686 Linux
medium Severity medium
: ---
: ---
Assigned To: Jay Fenlason
Brock Organ
Depends On:
  Show dependency treegraph
Reported: 2003-03-29 09:18 EST by Bob Scharle
Modified: 2014-08-31 19:24 EDT (History)
1 user (show)

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Last Closed: 2003-08-07 11:12:55 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 Bob Scharle 2003-03-29 09:18:54 EST
From Bugzilla Helper:
User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:0.9.4) Gecko/20011019

Description of problem:
xinetd uses 98% cpu
I did a cold install on a 2.4GHz P4 with 512 MB memory

Version-Release number of selected component (if applicable):

How reproducible:

Steps to Reproduce:
1.Cold install RH 8.0
3.run 'top'

Additional info:
Comment 1 Bob Scharle 2003-04-06 03:18:49 EDT
What is the status of this problem.  I can not run xinet thus rendering this
version of Red Hat unusable and therefore a waste of $175.00 which is a lot of
Comment 2 Jay Fenlason 2003-04-08 17:28:02 EDT
WORKSFORME on all the machines I've tried: a dual P4xeon-2G, a celeron 500, and
an Athlon 750.  Since I can't reproduce it here, I'm not going to be able to
debug this without a lot of legwork on your part.

What is your network configuration like?  What packages did you install?  Do any
of your log files have any useful information in them?  What does "strace -p
(the pid of the xinetd process)" show?  Etc.
Comment 3 Bob Scharle 2003-04-08 21:54:44 EDT
I really don't have the time to debug your software.  It should not be be my
responsibility to debug your software.  I would very much like a refund since
your software does not work.  I did notice that there is another ticket with the
same problem.  I also find it very hard to believe that you can not reproduce
the same problem.  Please let me know what the procedures are to get a full
refund so that I can purchase another vendors version of Linux.
Comment 4 Bob Scharle 2003-04-14 19:55:08 EDT
What is the status of the bug?   What are the procedures for a refund on
software that does not work?  If you are unable to answer my questions please
forward me the name and email address of your manager.  I DO NOT want to hear it
works for me.  I either want this bug fixed or my money back.
Comment 5 Tim Burke 2003-04-15 09:33:07 EDT
It is common practice that in the course of diagnosing problems that we request
the customer provide us the information we need to go on.  This is not unique to
Linux, where the spirit of cooperation is supposed to be even stronger.

Please provide us more information to help us reproduce and address the problem
you are encountering.  What is your hardware configuration?  What are the
contents of your xinetd.d?  Given that the xinetd.d contents are generally
tailored per site, we would like to know how yours is configured.
Comment 6 Jay Fenlason 2003-04-17 15:48:47 EDT
Please download the xinetd-2.3.11-1.8.0.i386.rpm file avaliable at
ftp://people.redhat.com/~fenlason/.xinetd/xinetd-2.3.11-1.8.0.i386.rpm  Then
install it (as root) with the command "rpm -Fvh xinetd-2.3.11-1.8.0.i386.rpm"
after cd-ing to the directory where you downloaded the xinetd-2.3.11-1.8.0.i386.rpm
Comment 7 Bob Scharle 2003-04-18 17:35:48 EDT
When I double click on the link it fails with the following message:

Failed to change directory

I tried to ftp to people.redhat.com and cd into fenlason/xinetd and that also
does not work.
Comment 8 Jay Fenlason 2003-04-21 11:33:31 EDT
If that doesn't work, try

Note the . in front of xinetd in the path--it's hard to see.

Comment 9 Bob Scharle 2003-04-25 14:02:34 EDT
I was able to download and install the xinetd from your web site and that seems
to have resolved the problem.  Thank you.
Comment 10 Jay Fenlason 2003-08-07 11:12:55 EDT
Closing this since the reporter says it is fixed.

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