$ Linux One Liners
Back to commands

Linux Survival Basics

Read-only

Print the Exact systemd Exit Fields

Full status output is useful for humans, but incident notes and scripts need compact fields like Result, ExecMainStatus, and restart count.

Command

systemctl show app-worker --property=Result,ExecMainCode,ExecMainStatus,NRestarts --no-pager

Before you run this

System impact: Read-only. Low when scoped to the shown target.

When not to use it: Do not treat numeric status values as self-explanatory; pair them with status or journal lines.

Expected output

Result, ExecMainCode, ExecMainStatus, and NRestarts property lines.

System impact

Read-only. Nothing changes. systemctl show prints selected unit properties.

Recovery / rollback: no state is changed.

When to use it

Use when documenting a failure, comparing before and after recovery, or writing a runbook check.

When not to use it

Do not treat numeric status values as self-explanatory; pair them with status or journal lines.

next steps

Related commands

Linux Survival Basics Read-only

Inspect One Service Without Pager Traps

Make systemctl status safe for scripts, screenshots, and quick incident notes.

systemctl status nginx --no-pager --lines=30
Linux Survival Basics Read-only

Show a Service LimitNOFILE

A shell ulimit is not the service limit.

systemctl show nginx -p LimitNOFILE --no-pager
Hosting Operations Read-only

Print Runtime Paths and User From systemd

Confirm the user, working directory, env file, and ExecStart systemd is actually using.

systemctl show app-worker --property=FragmentPath,DropInPaths,EnvironmentFiles,ExecStart,User,WorkingDirectory --no-pager
Study mapping

Use this as independent command practice: read the notes, predict the output, then compare it with the example before using a real shell.

  • LPIC-1 style command-line practice
  • LFCS style performance-task practice
  • Linux+ style troubleshooting review

Independent study support only. No affiliation, endorsement, exam dumps, or real exam questions.