Back to commands

Hosting Operations

Read-only, can be slow

List Newest Source Files Before Backup

You need a timestamp-sorted view of source files before comparing backups.

Command

find source -type f -printf '%TY-%Tm-%Td %TH:%TM %p\n' | sort

Before you run this

System impact: Read-only. Can create load on large logs, directories, filesystems, or process tables.

When not to use it: Do not use it as proof that backup contents match; pair it with checksums or rsync dry runs.

Expected output

A sorted list of source files with modification timestamps.

System impact

Read-only, can be slow. Nothing changes. The command reads file timestamps and paths.

Scope this to the smallest useful path or service on busy systems.

Recovery / rollback: no state is changed.

When to use it

Use before backup checks or when you need to understand recent source changes.

When not to use it

Do not use it as proof that backup contents match; pair it with checksums or rsync dry runs.

Explanation-only example

Illustrated output, not a live lab run

This example is intentionally illustrative. It shows the command shape without killing real processes or changing your machine.

demo@lab:~$

$ find source -type f -print | sort

source/app/config.yml
source/assets/logo.svg
source/content/about.md
source/content/index.md

$ find source -type f -printf '%TY-%Tm-%Td %TH:%TM %p\n' | sort

2026-06-25 12:10 source/content/index.md
2026-06-26 00:27 source/app/config.yml
2026-06-26 00:27 source/assets/logo.svg
2026-06-26 00:27 source/content/about.md
View commands shown

These are the commands shown in the sanitized transcript.

Commands shown

  1. find source -type f -print | sort
  2. find source -type f -printf '%TY-%Tm-%Td %TH:%TM %p\n' | sort

next steps

Related commands

Hosting Operations Can be slow

List Restore Points Before a Drill

A restore drill starts by proving which backups actually exist.

cd restore-dr && find backups -maxdepth 2 -type f -name MANIFEST.txt -printf '%TY-%Tm-%Td %TH:%TM %h\n' | sort -r
Hosting Operations Can be slow

List Newest Build Artifacts

Confirm what your pipeline actually produced before you deploy it.

find artifacts/ -type f -printf '%TY-%Tm-%Td %TH:%TM %10s %p\n' | sort | tail -20
Hosting Operations Can be slow

Find the Newest Build Logs First

The failing file is usually one of the newest artifacts.

find artifacts logs -type f \( -name '*.log' -o -name '*.txt' \) -printf '%TY-%Tm-%Td %TH:%TM %p\n' | sort -r | head
Hosting Operations Can be slow

Show Release Directory Ages

See your newest release directories without opening a dashboard.

find releases/ -mindepth 1 -maxdepth 1 -type d -printf '%T@ %TY-%Tm-%Td %TH:%TM %p\n' | sort -nr | head -10 | cut -d' ' -f2-
Hosting Operations Can be slow

Review Log Files Before Cleanup

Before truncating logs, prove which log files are large and how old they are.

find /lab/disk-inode-cleanup/var/log -xdev -type f -printf '%10s %TY-%Tm-%Td %p\n' | sort -nr
Study mapping

Use this as independent command practice: read the notes, predict the output, then compare it with the example before using a real shell.

  • lpic1:103-gnu-unix-commands
  • lpic1:104-filesystems-permissions-fhs
  • lfcs:essential-commands
  • lfcs:operations-deployment
  • lfcs:services-logs
  • lfcs:storage
  • linuxplus:automation-scripting
  • linuxplus:provisional
  • linuxplus:system-management
  • risk:read-only

Useful for

  • LPIC-1 style command-line practice
  • LFCS style performance tasks
  • Linux+ style troubleshooting review

Independent study support only. No affiliation, endorsement, exam dumps, or real exam questions.