Inspect Linux processes with ps, top, and pgrep
Compare a point-in-time process snapshot with live CPU and memory activity, then verify the owning command before taking action.
Read guide →LINUX · FIELD GUIDES
Practical Linux administration guides for processes, services, files, permissions, networking, packages, and shell operations.
Compare a point-in-time process snapshot with live CPU and memory activity, then verify the owning command before taking action.
Read guide →Identify a process, request graceful shutdown, and verify it exited before considering stronger signals.
Read guide →Inspect a systemd unit, distinguish starting from enabling, and verify a deliberate service change.
Read guide →Filter systemd logs by unit and time, follow new entries, and preserve context around the first failure.
Read guide →Use du and find to locate space consumers while keeping the scan within the relevant filesystem.
Read guide →Separate filesystem capacity from directory usage, and check inode availability as well as bytes.
Read guide →Read owner, group, and mode bits; check directory traversal and ACLs; then make a narrow ownership or mode adjustment.
Read guide →Inspect account records with getent and id, then make a narrowly scoped group change.
Read guide →Search a bounded tree by name or content, and pass filenames safely when names may contain spaces.
Read guide →Understand standard input/output, pipes, overwrites, quoting, pipeline status, and command exit codes in Bash.
Read guide →Start scripts with explicit input checks, quoted variables, and predictable cleanup for temporary files.
Read guide →Inspect shell variables, create and safely inspect tar archives, and distinguish a symbolic link from its target.
Read guide →Use iproute2 to inspect links, assigned addresses, and the route selected for a destination.
Read guide →Separate ICMP reachability, DNS lookup, TCP connection, TLS negotiation, and HTTP response checks.
Read guide →List listening TCP and UDP sockets, check bind addresses, and identify process ownership when permitted.
Read guide →Compare application-style name service lookup with a direct DNS query, then inspect which service manages resolver settings.
Read guide →Identify the distribution family, refresh package metadata, review proposed updates, and verify the installed software.
Read guide →Inspect a user crontab and systemd timers, then trace a missed job through its command, environment, and logs.
Read guide →