htop upgrade to 0.9, extra empty processes now shown
 

Hi everyone

I run CentOS 5.5 and use htop from the dag wieers repo. I ran an upgrade on the machine recently and htop was an upgraded package to v0.9.

But now when I run htop there's about a screen and a half's worth of these extra processes with an empty command value (see screenshot).
Anyone know what these are, or if it's possible to hide them in htop?

I've tried restarting after the upgrade and they're still there.

Any ideas?

Cheers, B

With pids in that range, they have to be kernel threads. Should have a command entry.
I just checked on an Arch system that also has v 0.9, and they all show o.k. Something wrong somewhere with your package. If you don't want to see them (at all), enter "K" (capital, no quotes) in htop.

Thanks for the info.

When pressing K all those threads are still displayed.
But the Tasks heading at the top changes slightly to display 0 kthr... which I guess means there are 0 kernel threads.
Strange!

This is a 64bit CentOS 5.5 installation.
Just updated another CentOS 5.5 64bit installation and htop on that machine is exhibiting the same behaviour.

Cheers, B

Hmmm - on mine the "kthr" disappears altogether.

Stranger and stranger said Alice ...

Pressing K sort of toggles "kthr" but when it's in view, it's 0!
I have also tried going in to htop options to try hiding kernel threads that way but it makes no difference

I'll post a message to the htop sourceforge mailing list and see if anyone's seen this before!

Cheers, B

I upgraded htop on my machine (RHEL5 64bit) a while back and noticed that also. I just downgraded because I couldn't find a way to toggle them off. If you find anything out, let us know because I am curious too.

Yeah I'll see if there's a solution on the htop sourceforge lists.
At least I'm not the only one then!

I think it might be something to do with the upgrade. When I did a fresh install of CentOS 5.5 and installed htop it worked fine.
Whereas the machines I was doing this on I was also upgrading from CentOS 5.4 at the same time with yum update.

I have the same issue as well. My servers are running 64 bit CentOS 5.5, I just recently upgraded them from 5.4.

Hasn't happened to me before the upgrade, and it only just appeared about two days ago. My machines have been up for a month and a half now since I upgraded.