Shell scripting · Lesson 15 of 31 · 8 minutes

Shell scripting checkpoint

Complete a mini script-review workflow.

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 script exists
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
Write checkpoint log
Run printf shell-checkpoint | tee lab/shell-checkpoint.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 shell-checkpoint | tee lab/shell-checkpoint.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.
3
Protect checkpoint log
Run chmod 600 lab/shell-checkpoint.txt.
Hint & worked example
Change permissions using an octal mode or a symbolic adjustment. Each rwx bit belongs to owner, group, or other.
The command outcome must match the task, including successful access or the explicitly requested failure.
```
chmod 600 lab/shell-checkpoint.txt
```
Remember: Do not use 777 as a blanket fix. Grant the smallest access needed.
4
Inspect checkpoint log
Run stat lab/shell-checkpoint.txt.
Hint & worked example
Inspect a file or directory metadata record, including ownership, permissions, and size.
The command outcome must match the task, including successful access or the explicitly requested failure.
```
stat lab/shell-checkpoint.txt
```
Remember: Metadata and file contents answer different questions.

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.
chmod: Change permissions using an octal mode or a symbolic adjustment. Each rwx bit belongs to owner, group, or other.
Do not use 777 as a blanket fix. Grant the smallest access needed.
stat: Inspect a file or directory metadata record, including ownership, permissions, and size.
Metadata and file contents answer different questions.

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.

$ printf shell-checkpoint | tee lab/shell-checkpoint.txt

shell-checkpoint

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

$ chmod 600 lab/shell-checkpoint.txt

(no output; exit 0)

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

$ stat lab/shell-checkpoint.txt

Path: /home/learner/lab/shell-checkpoint.txt
Type: file
Mode: -rw-------
Owner: learner
Group: learners
Size: 16 bytes

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 “Shell scripting checkpoint”, which interpretation is safe?A command appearing in history proves it completed successfully.A successful first check guarantees that every dependent service is healthy.A format string controls output; a newline is data, not an automatic guarantee.

Apply it elsewhere

Before adapting the printf workflow from “Shell scripting checkpoint” 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: Shebang reading 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