The ps command uses the following syntax: ps įrequently used ps command options include:

Unlike the other commands on this list, ps presents the output as a static list, not updated in real time. The ps Linux command creates a snapshot of currently running processes. List Running Processes in Linux by Using the ps Command You can also combine the ps command with the pgrep command to identify individual processes. To list currently running processes, use the ps, top, htop, and atop Linux commands. There is a bit of a learning curve with SELinux and too much for a simple answer, but I would never ever disable it on a public facing server.Note: Learn more about terminating Linux processes in our guide to killing processes in Linux. I would recommend you read this document about SELinux first and this document to get an overview and then look at documents like this for your distribution. Most of the time it happens when you added files to the system without setting the correct SELinux permissions or a process tries to access a non typical file or folder. This package is a set of tools that can help you to find the real cause of the SELinux violation. I would recommend to use tail -f /var/log/audit/audit.log to see live changes of the file.īecause you have high CPU load of setroubleshootd I assume you have permanent changes/entries in the file, meaning something permanently violates the SELinux policy and the output could give you a first clue why.įor more in depth troubleshooting you could install setroubleshoot-server with yum install setroubleshoot-server. If the current mode is permissive, then SELinux does not block anything but only logs it (good for troubleshooting).Īssuming SELinux is enabled and in in enforcing mode, now take a look at the log /var/log/audit/audit.log. The interesting parts are SELinux status: and Current Mode which are usually enabled and enforcing. Try to find out in which mode SELinux is running on the machine by typing sestatus. So what could cause the high CPU usage of setroubleshootd. First of all, you should not disable SELinux.

Linux cpu usage by process