Server operations · Lesson 7 of 36 · 8 minutes

Service files

Inspect simulated unit files and journals together.

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
Show 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
Read unit file
Run cat /etc/systemd/system/nginx.service.
Hint & worked example
Read one or more files to standard output without editing their contents.
The command outcome must match the task, including successful access or the explicitly requested failure.
```
cat /etc/systemd/system/nginx.service
```
Remember: Reading a source file should precede changing it; avoid printing real secrets.
3
Read journal
Run journalctl -u nginx.
Hint & worked example
Read the training journal by unit or a bounded line window.
The command outcome must match the task, including successful access or the explicitly requested failure.
```
journalctl -u nginx
```
Remember: A relevant unit and time range are more useful than an unfiltered wall of logs.

Understand the pattern

A complete service review includes config and runtime evidence.

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.
cat: Read one or more files to standard output without editing their contents.
Reading a source file should precede changing it; avoid printing real secrets.
journalctl: Read the training journal by unit or a bounded line window.
A relevant unit and time range are more useful than an unfiltered wall of logs.

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.

$ cat /etc/systemd/system/nginx.service

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

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

$ journalctl -u nginx

May 26 08:10:00 clairos-learn nginx[42]: configuration file syntax is ok
May 26 08:10:01 clairos-learn nginx[42]: started static training site
May 26 08:20:05 clairos-learn nginx[42]: access denied for /api/test by static rule

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 “Service files”, which interpretation is safe?Reading a source file should precede changing it; avoid printing real secrets.A command appearing in history proves it completed successfully.A successful first check guarantees that every dependent service is healthy.

Apply it elsewhere

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

Keep the momentum.

Complete the lab, then explain and apply the pattern.

Next: Nginx site map 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