Diagnose a Failed systemd Service Without Guessing
Use status, show, journalctl, unit dependencies, and a disposable user service to turn a failed unit into an exact exit reason.
10 min read
Topic
8 articles
Process creation, execution, signals, and lifecycle behavior.
Use status, show, journalctl, unit dependencies, and a disposable user service to turn a failed unit into an exact exit reason.
10 min read
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
Follow ls -la from a terminal keystroke through shell parsing, command lookup, process replacement, filesystem calls, and pixels on screen.
11 min read
Replace the punctuation model of `|` with connected processes, file descriptors, bounded kernel buffers, and backpressure.
12 min read
Build a reliable journalctl workflow by separating boot selection, unit filters, time windows, priority, and persistent storage.
13 min read
Keep everyday automation portable by treating the shell as a language boundary, checking tools explicitly, and testing the unhappy path.
10 min read