On Monday 31 August 2009 15:20:46 Karl Sinn wrote:
Maybe not. There is a bug in nscd that causes it to restart itself with "exe" as a process name, if it is run in paranoia mode. It was reported to red hat at
https://bugzilla.redhat.com/show_bug.cgi?id=490010
I can't find it in our bugzilla, but our code definitely has the same problem. To reproduce, enable paranoid mode in nscd, and set the restart interval to something low so you don't have to wait too long to see the problem. Then just wait for it to be restarted.
Note that "ps" will still report the real process name, but top reports the false "exe" one (they read the name from different places in /proc)
Perhaps that is hitting here. It wouldn't totally surprise me to see nscd spinning with 100% CPU. But comparing the ps output with the top output might show the truth.
Do I understand that it's not a big problem, and I can just kill the process?
If you can confirm that the process you are seeing is indeed nscd (by searching for the process ID in the "ps aux" output and seeing what it's name is there) then yes, it's not a big problem. It's obviously still a bug in nscd though Anders -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org