Server operations · Lesson 32 of 36 · 8 minutes

Unit file reading

Read a service definition before interpreting its runtime state.

Open the lab Course map

Mastery 0/3Run itExplain itApply it

learner@clairos:~ $

↑ history · Tab complete · Ctrl+C cancel · Esc, Tab to leaveExit 0

Your objectives

Hints are always available. Wrong turns never cost XP.

1
Read the nginx unit
Run systemctl cat nginx.
Hint & worked example
Inspect or change a simulated systemd service. Status, active state, and unit configuration reveal different evidence.
The command outcome must match the task, including successful access or the explicitly requested failure.
```
systemctl cat nginx
```
Remember: A service can be active while an application endpoint is unhealthy; verify both layers.
2
Find the start command
Run grep ExecStart /etc/systemd/system/nginx.service.
Hint & worked example
Select input lines that match a pattern; -i ignores case, -n adds line numbers, and -v inverts selection.
The command outcome must match the task, including successful access or the explicitly requested failure.
```
grep ExecStart /etc/systemd/system/nginx.service
```
Remember: No matches is exit status 1, which is different from a malformed invocation.
3
Compare the runtime state
Run systemctl status nginx.
Hint & worked example
Inspect or change a simulated systemd service. Status, active state, and unit configuration reveal different evidence.
The command outcome must match the task, including successful access or the explicitly requested failure.
```
systemctl status nginx
```
Remember: A service can be active while an application endpoint is unhealthy; verify both layers.

Understand the pattern

Connecting a systemd unit definition to service behavior helps operators explain what they know before they change anything.

systemctl: Inspect or change a simulated systemd service. Status, active state, and unit configuration reveal different evidence.
A service can be active while an application endpoint is unhealthy; verify both layers.
grep: Select input lines that match a pattern; -i ignores case, -n adds line numbers, and -v inverts selection.
No matches is exit status 1, which is different from a malformed invocation.

Worked example and expected result

$ systemctl cat nginx

[Unit]
Description=fake nginx
[Service]
ExecStart=/usr/sbin/nginx -g 'daemon off;'

Exit status: 0. The command completed successfully in the training fixture.

$ grep ExecStart /etc/systemd/system/nginx.service

ExecStart=/usr/sbin/nginx -g 'daemon off;'

Exit status: 0. The command completed successfully in the training fixture.

$ systemctl status nginx

nginx.service - simulated nginx
   Loaded: loaded
   Active: active
   Notes: serving the simulated static learn site

Exit status: 0. The command completed successfully in the training fixture.

Try a variation

Repeat this workflow in the sandbox with a different scratch filename. Keep the system fixtures unchanged and compare the observed output with your expectation before moving on.

Explain it

In “Unit file reading”, which interpretation is safe?A command appearing in history proves it completed successfully.A successful first check guarantees that every dependent service is healthy.No matches is exit status 1, which is different from a malformed invocation.

Apply it elsewhere

Before adapting the grep workflow from “Unit file reading” to another server, what should you do?Skip output inspection whenever the command is familiar.Confirm the current directory, target identity, permissions, and the installed command behavior first.Paste the training paths unchanged into production.

Keep the momentum.

Complete the lab, then explain and apply the pattern.

Next: Service state triangulation Try an incident drill

Anonymous lesson and mastery progress lasts for this session. Sign in to keep synced lesson XP between sessions; mastery stays device-local. No speed bonus, lost lives, or hint penalties.

Keep learning

GNU Coreutils manual · GNU Bash manual