SIGTERM Before SIGKILL: How Linux Process Shutdown Actually Works
Signals request process actions; a safe lab shows SIGTERM running cleanup with exit 0 while SIGKILL bypasses handlers and yields status 137.
9 min read
Section
7 articles
Clear explanations of the Linux concepts that make troubleshooting easier.
Signals request process actions; a safe lab shows SIGTERM running cleanup with exit 0 while SIGKILL bypasses handlers and yields status 137.
9 min read
Namespaces change what processes can see; cgroups account for and limit resources. Inspect both without pretending a container is a tiny VM.
10 min read
Read Linux load average as a queue signal, separate runnable work from uninterruptible waits, and pair the three familiar numbers with CPU count and PSI.
12 min read
A practical command map for inspecting Linux first, then changing files, processes, storage, networking, logs, users, and packages with portability boundaries visible.
16 min read
Replace the punctuation model of `|` with connected processes, file descriptors, bounded kernel buffers, and backpressure.
12 min read
Read RAM as anonymous memory, reclaimable cache, kernel state, swap, and pressure—then separate host capacity from cgroup limits.
14 min read
Build a reliable journalctl workflow by separating boot selection, unit filters, time windows, priority, and persistent storage.
13 min read