Text and logs · Lesson 24 of 38 · 8 minutes

Logrotate dry run

Dry-run log rotation without moving files.

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
Dry-run rotation
Run logrotate -d /etc/logrotate.d/nginx.
Hint & worked example
Inspect or dry-run a simulated log-rotation policy.
The command outcome must match the task, including successful access or the explicitly requested failure.
```
logrotate -d /etc/logrotate.d/nginx
```
Remember: A dry run reports intended behavior without rotating real logs.
2
Find rotated logs
Run find /var/log -name .1.
Hint & worked example
Search directory trees by criteria rather than relying on one shallow listing.
The command outcome must match the task, including successful access or the explicitly requested failure.
```
find /var/log -name .1
```
Remember: Quote wildcard patterns so find receives them instead of the shell expanding them first.
3
Read rotated access log
Run tail -n 2 /var/log/nginx-access.log.1.
Hint & worked example
Show the end of an input; -n selects the number of lines.
The command outcome must match the task, including successful access or the explicitly requested failure.
```
tail -n 2 /var/log/nginx-access.log.1
```
Remember: This browser lab snapshots output; it does not keep a live tail -f stream.

Understand the pattern

Junior operators build confidence by gathering evidence before changing systems.

logrotate: Inspect or dry-run a simulated log-rotation policy.
A dry run reports intended behavior without rotating real logs.
find: Search directory trees by criteria rather than relying on one shallow listing.
Quote wildcard patterns so find receives them instead of the shell expanding them first.
tail: Show the end of an input; -n selects the number of lines.
This browser lab snapshots output; it does not keep a live tail -f stream.

Worked example and expected result

$ logrotate -d /etc/logrotate.d/nginx

debug: reading /etc/logrotate.d/nginx
debug: rotation pattern accepted
debug: would rotate /var/log/nginx-access.log and /var/log/nginx-error.log
/var/log/nginx-*.log {
  daily
  rotate 7
  compress
  missingok
  notifempty
}

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

$ find /var/log -name .1

/var/log/nginx-access.log.1
/var/log/nginx-error.log.1

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

$ tail -n 2 /var/log/nginx-access.log.1

127.0.0.1 GET /unix/courses/ 200
127.0.0.1 GET /missing 404

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 “Logrotate dry run”, which interpretation is safe?Quote wildcard patterns so find receives them instead of the shell expanding them first.A command appearing in history proves it completed successfully.A successful first check guarantees that every dependent service is healthy.

Apply it elsewhere

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

Keep the momentum.

Complete the lab, then explain and apply the pattern.

Next: Journal time window 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