Shell scripting · Lesson 17 of 31 · 8 minutes

Set eu review

Recognize strict-mode style script guards.

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
Find strict guard
Run grep "set -eu" scripts/deploy.sh.
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 "set -eu" scripts/deploy.sh
```
Remember: No matches is exit status 1, which is different from a malformed invocation.
2
Read script
Run cat scripts/deploy.sh.
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 scripts/deploy.sh
```
Remember: Reading a source file should precede changing it; avoid printing real secrets.
3
Hash script
Run sha256sum scripts/deploy.sh.
Hint & worked example
Compare content digests to detect byte changes, not to establish who authored the file.
The command outcome must match the task, including successful access or the explicitly requested failure.
```
sha256sum scripts/deploy.sh
```
Remember: A checksum detects changes only relative to a trusted expected digest.

Understand the pattern

Junior operators build confidence by gathering evidence before changing systems.

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.
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.
sha256sum: Compare content digests to detect byte changes, not to establish who authored the file.
A checksum detects changes only relative to a trusted expected digest.

Worked example and expected result

$ grep "set -eu" scripts/deploy.sh

set -eu

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

$ cat scripts/deploy.sh

#!/bin/sh
set -eu
echo fake deploy: build static files
echo fake deploy: run nginx -t

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

$ sha256sum scripts/deploy.sh

f7d569c8d8504a5ddbe9ac442362c65f068aeacd1f540b24ca1ec84b7c27359e  /home/learner/scripts/deploy.sh

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

Apply it elsewhere

Before adapting the cat workflow from “Set eu review” 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 guard checks 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