ipdetecto.com logo
ipdetecto.com
My IPSpeed
Knowledge Hub
HomeKnowledge HubLinux Process Management Commands
© 2026 ipdetecto.com
support@ipdetecto.comAboutContactPrivacyTermsllms.txt
Troubleshooting
5 MIN READ
Apr 19, 2026

Linux Process Management Commands

List, signal, and inspect processes: ps, pgrep, kill, nice, and cgroup-aware tools like systemd-cgtop.

Processes are identified by PID and live in namespaces and cgroups. ps aux lists user processes; pgrep finds PIDs by pattern. Signals like SIGTERM allow graceful shutdown; SIGKILL cannot be handled—use sparingly. nice and ionice adjust scheduling priorities. top and htop show live CPU and memory; systemd-cgtop attributes usage to units.

SignalNumberTypical use
SIGTERM15Polite stop
SIGKILL9Force kill hung tasks
SIGHUP1Reload configs for daemons

Related

systemctl, ss, sysadmin commands, sudo

Frequently Asked Questions

Q.What is the difference between kill and killall?

kill targets PIDs; killall matches by process name—riskier on shared binaries.

Q.When should I use SIGKILL?

Only when SIGTERM fails and the process is wedged—SIGKILL prevents cleanup and may corrupt data.

Q.How do I list child processes?

Use ps --forest, pstree, or /proc/$pid/task depending on depth needed.

Q.What does ps aux mean?

BSD-style columns: all users, user-oriented format, and processes without controlling terminals.

Q.How can I limit CPU for a runaway job?

Use systemd-run --scope -p CPUQuota= or cgroups tools; nice only nudges scheduling.

Q.Why does top show high steal time?

The VM hypervisor took CPU from the guest—check host contention, not app code first.

Q.What is a zombie process?

A child that exited but was not reaped—usually a parent bug; killing the parent may clear it.

Q.How do I trace syscalls for debugging?

Use strace with -p PID for live syscall tracing—expect overhead on production sparingly.
TOPICS & TAGS
pskilllinux processessignalstop