Shell scripting · Lesson 18 of 31 · 8 minutes

Script guard checks

Check required files before script-style work.

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
Check deploy file
Run test -f scripts/deploy.sh.
Hint & worked example
Evaluate a file or string condition through its exit status rather than printed output.
The command outcome must match the task, including successful access or the explicitly requested failure.
```
test -f scripts/deploy.sh
```
Remember: A successful test usually prints nothing; inspect $? or chain a command.
2
Check lab directory
Run test -d lab.
Hint & worked example
Evaluate a file or string condition through its exit status rather than printed output.
The command outcome must match the task, including successful access or the explicitly requested failure.
```
test -d lab
```
Remember: A successful test usually prints nothing; inspect $? or chain a command.
3
Write guard marker
Run printf guards-ok | tee lab/guards.txt.
Hint & worked example
Format data deliberately, including separators and final newlines. Copy a stream both to a file and standard output; -a appends.
The command outcome must match the task, including successful access or the explicitly requested failure.
```
printf guards-ok | tee lab/guards.txt
```
Remember: A format string controls output; a newline is data, not an automatic guarantee. tee can overwrite a file even though the output is also visible on screen.

Understand the pattern

Junior operators build confidence by gathering evidence before changing systems.

test: Evaluate a file or string condition through its exit status rather than printed output.
A successful test usually prints nothing; inspect $? or chain a command.
printf: Format data deliberately, including separators and final newlines.
A format string controls output; a newline is data, not an automatic guarantee.
tee: Copy a stream both to a file and standard output; -a appends.
tee can overwrite a file even though the output is also visible on screen.

Worked example and expected result

$ test -f scripts/deploy.sh

(no output; exit 0)

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

$ test -d lab

(no output; exit 0)

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

$ printf guards-ok | tee lab/guards.txt

guards-ok

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 “Script guard checks”, which interpretation is safe?A successful first check guarantees that every dependent service is healthy.A successful test usually prints nothing; inspect $? or chain a command.A command appearing in history proves it completed successfully.

Apply it elsewhere

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

Keep the momentum.

Complete the lab, then explain and apply the pattern.

Next: Script log capture 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