Linux Survival Basics

Inspect One Service Without Pager Traps

systemctl status can open a pager, wrap awkwardly, or hide the prompt during a tense server check.

Command

systemctl status nginx --no-pager --lines=30

What changed

Nothing changes. systemd prints the service state, main PID, resource summary, and recent logs.

Danger

safe

When to use it

Use when confirming whether a specific service is active, failed, restarting, or blocked on startup.

When not to use it

Do not use when you need long historical logs; use journalctl for a wider time range.

Undo or recovery

No undo needed because the command is read-only.

Expected output

Active state, main PID, memory, and recent service lines.

demo script

Disposable terminal steps

systemctl status nginx --no-pager --lines=30
systemctl is-active nginx

Terminal transcript Demo JSON

simulated output

What it looks like

disposable vessel

::fixture-ready::
$ systemctl status nginx --no-pager --lines=30
● nginx.service - A high performance web server
     Loaded: loaded (/lib/systemd/system/nginx.service; enabled)
     Active: active (running) since Thu 2026-06-25 14:12:10 CDT; 18min ago
   Main PID: 842 (nginx)
      Tasks: 3
     Memory: 12.4M
Jun 25 14:12:10 vps nginx[842]: start worker processes
Jun 25 14:12:11 vps nginx[842]: ready for connections
::exit-code::0
$ systemctl is-active nginx
active
::exit-code::0

YouTube Short

systemctl status without getting stuck.

For one service, disable the pager and cap log lines. You get useful state without flooding the terminal.

experiments

A/B tests to run

Metric: average_view_duration

A: Avoid getting trapped in less.

B: Make incident screenshots readable.