Linux - Software This forum is for Software issues.
Having a problem installing a new program? Want to know which application is best for the job? Post your question in this forum. |
Notices |
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
Are you new to LinuxQuestions.org? Visit the following links:
Site Howto |
Site FAQ |
Sitemap |
Register Now
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
|
|
07-02-2003, 08:02 AM
|
#1
|
LQ Newbie
Registered: Dec 2002
Location: USA
Posts: 23
Rep:
|
'Top' utility floating point error
Have a strange problem here. On a pretty much "stock" installation of RH 7.2, I can't run the 'top' command. I figured perhaps if I could find the rpm that provides 'top' to begin with, then perhaps a forced reinstall would work. Unfortunately, I can't seem to find that. The closest I get is libgtop, and it seems to provide the related libraries, but not the binary. Also, the one of the machines in the environment is able to run 'top' w/o the libgtop package (accoring to rpm-qa | grep libgtop), so there goes my theory there.
Anyhow, this is the error I get:
5:44pm up 428 days, 3:04, 1 user, load average: 0.03, 0.04, 0.00
37 processes: 36 sleeping, 1 running, 0 zombie, 0 stopped
Floating point exception
[user@server2 user]$
[user@server2 user]$
[user@server2 user]$ rpm -qa | grep libgtop
libgtop-1.0.12-4
Anyone have any suggestions for me? I could really use the help.
|
|
|
07-23-2003, 12:13 PM
|
#2
|
Member
Registered: Feb 2002
Location: IL
Distribution: Ubuntu currently, also Fedora, RHEL, CentOS
Posts: 111
Rep:
|
The rpm is in procps-*
but that may not fix your problem, as I am having it too.
|
|
|
07-23-2003, 10:07 PM
|
#3
|
LQ Newbie
Registered: Dec 2002
Location: USA
Posts: 23
Original Poster
Rep:
|
Quote:
Originally posted by mastahnke
The rpm is in procps-*
but that may not fix your problem, as I am having it too.
|
What is even stranger is that top started working again for a while. I just assumed our cranky sysadmin had fixed it himself, but didn't tell anyone (as usual). I found later than again, it started happening again. I am now completely at a loss as to how this could only happen intermittantly. I get a "floating point" error on 4 different machines that are set up almost identically.
If anyone has any ideas other than just re-installing the default package or even installing an updated one, please let me know...
thx.
|
|
|
07-23-2003, 10:55 PM
|
#4
|
Member
Registered: Feb 2002
Location: IL
Distribution: Ubuntu currently, also Fedora, RHEL, CentOS
Posts: 111
Rep:
|
I am that cranky system admin, and I tried reinstalling it and no dice. The only other thing I could think would be a reboot, but that isn't going to happen. Not when uptime is everything and some of these systems are going on 1.5 years worth of uptime.
I will keep trying though.
MIKE
|
|
|
07-24-2003, 06:18 AM
|
#5
|
LQ Newbie
Registered: Dec 2002
Location: USA
Posts: 23
Original Poster
Rep:
|
Quote:
Originally posted by mastahnke
I am that cranky system admin, and I tried reinstalling it and no dice. The only other thing I could think would be a reboot, but that isn't going to happen. Not when uptime is everything and some of these systems are going on 1.5 years worth of uptime.
I will keep trying though.
MIKE
|
haha... just the fact that you're replying on this means that you aren't as cranky as our sysadmin!
I really do appreciate the assist on this, and yes, uptime is important. I suppose if the reboot is the true solution here, then so be it... I could advise on scheduling one if necessary.
Before that though, I think I'll see if I can figure out what's really wrong.
|
|
|
All times are GMT -5. The time now is 02:38 AM.
|
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.
|
Latest Threads
LQ News
|
|