"top" starts to use 100% of CPU if run under rootsh, and ssh session ends unexpectedly

Solution Verified - Updated -

Issue

If "top" runs as root from the rootsh, and the ssh session unexpectedly ends (temporary network issue), this process gets stuck and causes high CPU usage.

Environment

Red Hat Enterprise Linux
rootsh-1.5.3

Subscriber exclusive content

A Red Hat subscription provides unlimited access to our knowledgebase of over 48,000 articles and solutions.

Current Customers and Partners

Log in for full access

Log In
Close

Welcome! Check out the Getting Started with Red Hat page for quick tours and guides for common tasks.