top segmentation fault
hi, I have a question about top (from the original 7.0 SuSE dist) that died, and so did the box, with a segmentation fault.... The box is a P166/64Mb with SuSE 7.0... many things have been updated (such as bind, postfix etc..). I ran top in order to see if everything was ok... I left the room 4 minutes and when i came back, the box was dead... I had to reset it... There has been no damage, everything restarted ok, but I'm scared to use top again, even for seconds only... Has anyone heard about such a problem ? or does it come from my install ?... TIA Stephane Parenton
* stephane parenton
hi,
I have a question about top (from the original 7.0 SuSE dist) that died, and so did the box, with a segmentation fault.... The box is a P166/64Mb with SuSE 7.0... many things have been updated (such as bind, postfix etc..). I ran top in order to see if everything was ok... I left the room 4 minutes and when i came back, the box was dead... I had to reset it... There has been no damage, everything restarted ok, but I'm scared to use top again, even for seconds only...
Has anyone heard about such a problem ? or does it come from my install ?...
You'd have to provide much more info on how you upgraded etc. etc. before that question can be answered. -- Mads Martin Joergensen, http://mmj.dk "Why make things difficult, when it is possible to make them cryptic and totally illogic, with just a little bit more effort." -- A. P. J.
Mads Martin Jørgensen wrote:
* stephane parenton
[May 10. 2001 09:51]: P166/64Mb with SuSE 7.0... many things have been updated (such as bind, postfix etc..). I ran top in order to see if everything was ok... I left the room 4 minutes and when i came back, the box was dead... I had to reset it... There has been no damage, everything restarted ok, but I'm scared to use top again, even for seconds only...
You'd have to provide much more info on how you upgraded etc. etc. before that question can be answered.
hi, I upgraded to rpm4, to Bind 9.1, upgraded postfix, upgraded squid, tripwire and openssh... then did my config. I haven't touched top. I always took the tar.gz things, and recompile them on the box. Every test done (make test for example when provided) was ok. bind runs right with no error generation, postfix also, squid is ok.... I have no error generation with activity... The only time the box fall down was after the top launching.... The box froze, with the message given, and I could only reset the box. please tell me if the infos are enough ... Regards Stephane
stephane, i posted a segmentation fault problem earlier too.. mine would turn up on any command. one time it'd be ls another time cp and once mysql. well my problem is fixed now. thanks to these guys esp. Ole. the problem is with the cpu cooler. make sure it's workin fine or u can do as i did. change it :) good luck jorge. On Thu, 10 May 2001, stephane parenton wrote:
hi,
I have a question about top (from the original 7.0 SuSE dist) that died, and so did the box, with a segmentation fault.... The box is a P166/64Mb with SuSE 7.0... many things have been updated (such as bind, postfix etc..). I ran top in order to see if everything was ok... I left the room 4 minutes and when i came back, the box was dead... I had to reset it... There has been no damage, everything restarted ok, but I'm scared to use top again, even for seconds only...
Has anyone heard about such a problem ? or does it come from my install ?...
TIA
Stephane Parenton
-- To unsubscribe send e-mail to suse-linux-e-unsubscribe@suse.com For additional commands send e-mail to suse-linux-e-help@suse.com Also check the FAQ at http://www.suse.com/support/faq and the archives at http://lists.suse.com
participants (3)
-
Mads Martin Jørgensen
-
stephane parenton
-
Th3 Hav3n's Keeper