Text and logs · Lesson 22 of 38 · 8 minutes

Text pipeline checkpoint

Combine search, field extraction, transform, and counting.

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
Extract denied process fields
Run grep denied /var/log/auth.log | awk '{print $5}'.
Hint & worked example
Select input lines that match a pattern; -i ignores case, -n adds line numbers, and -v inverts selection. Extract whitespace-delimited fields with the supported print patterns.
The command outcome must match the task, including successful access or the explicitly requested failure.
```
grep denied /var/log/auth.log | awk '{print $5}'
```
Remember: No matches is exit status 1, which is different from a malformed invocation. Quote awk programs so shell variable expansion does not consume $1; single quotes are usually appropriate.
2
Normalize incident text
Run printf incident | tr a-z A-Z.
Hint & worked example
Format data deliberately, including separators and final newlines. Translate or remove supported character sets from a stream.
The command outcome must match the task, including successful access or the explicitly requested failure.
```
printf incident | tr a-z A-Z
```
Remember: A format string controls output; a newline is data, not an automatic guarantee. tr operates on characters, not whole words or regular-expression matches.
3
Count denied lines
Run grep denied /var/log/auth.log | wc -l.
Hint & worked example
Select input lines that match a pattern; -i ignores case, -n adds line numbers, and -v inverts selection. 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.
```
grep denied /var/log/auth.log | wc -l
```
Remember: No matches is exit status 1, which is different from a malformed invocation. 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.

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.
awk: Extract whitespace-delimited fields with the supported print patterns.
Quote awk programs so shell variable expansion does not consume $1; single quotes are usually appropriate.
printf: Format data deliberately, including separators and final newlines.
A format string controls output; a newline is data, not an automatic guarantee.
tr: Translate or remove supported character sets from a stream.
tr operates on characters, not whole words or regular-expression matches.
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

$ grep denied /var/log/auth.log | awk '{print $5}'

sshd[118]:
sshd[141]:

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

$ printf incident | tr a-z A-Z

INCIDENT

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

$ grep denied /var/log/auth.log | wc -l

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 “Text pipeline 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 “Text pipeline 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: Logrotate config 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