Shell scripting · Lesson 19 of 31 · 8 minutes

Script log capture

Capture script-style output into a log file.

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
Capture deploy marker
Run printf deploy-check | tee lab/deploy.log.
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 deploy-check | tee lab/deploy.log
```
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.
2
Read deploy log
Run cat lab/deploy.log.
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 lab/deploy.log
```
Remember: Reading a source file should precede changing it; avoid printing real secrets.
3
Count deploy log
Run wc -l lab/deploy.log.
Hint & worked example
Count input. -l counts newline characters, -w counts whitespace-delimited words, and -c counts bytes.
The command outcome must match the task, including successful access or the explicitly requested failure.
```
wc -l lab/deploy.log
```
Remember: Text without a final newline may have fewer counted lines than visible rows.

Understand the pattern

Junior operators build confidence by gathering evidence before changing systems.

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.
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.
wc: Count input. -l counts newline characters, -w counts whitespace-delimited words, and -c counts bytes.
Text without a final newline may have fewer counted lines than visible rows.

Worked example and expected result

$ printf deploy-check | tee lab/deploy.log

deploy-check

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

$ cat lab/deploy.log

deploy-check

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

$ wc -l lab/deploy.log

0 lab/deploy.log

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 log capture”, 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 “Script log capture” 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: Path helper script review 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