$ Linux One Liners
Back to commands

Hosting Operations

Read-only, can be slow

Find Files Newer Than a Backup Snapshot

You need to list source files changed after the backup snapshot marker.

Command

find source -type f -newer backup/.snapshot -print | 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 timestamp checks as the only integrity signal; clock skew and preserved mtimes can mislead.

Expected output

Source files newer than the backup snapshot marker.

System impact

Read-only, can be slow. Nothing changes. The command compares source file mtimes to the snapshot marker.

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

Recovery / rollback: no state is changed.

When to use it

Use when checking what changed since the last backup ran.

When not to use it

Do not use timestamp checks as the only integrity signal; clock skew and preserved mtimes can mislead.

Watch this command run

Command transcript

This sanitized transcript shows the commands and output shape without exposing host details.

demo@lab:~$

$ stat -c '%y %n' backup/.snapshot source/content/index.md

2026-06-25 12:05:00.000000000 +0000 backup/.snapshot
2026-06-25 12:10:00.000000000 +0000 source/content/index.md

$ find source -type f -newer backup/.snapshot -print | sort

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

These are the commands shown in the sanitized transcript.

Commands shown

  1. stat -c '%y %n' backup/.snapshot source/content/index.md
  2. find source -type f -newer backup/.snapshot -print | sort

next steps

Related commands

Hosting Operations Can be slow

Compare Source and Backup File Lists

A backup can be missing files and still look plausible at a glance.

comm -3 <(find source -type f | sed 's#^source/##' | sort) <(find backup -type f | sed 's#^backup/##' | sort)
Hosting Operations Can be slow

List Newest Source Files Before Backup

Before trusting a backup, know which files changed most recently.

find source -type f -printf '%TY-%Tm-%Td %TH:%TM %p\n' | sort
Hosting Operations Can be slow

List Largest Files in a Backup

Large backup files are where storage surprises usually start.

find backup -type f -printf '%s %p\n' | sort -nr | head
Hosting Operations Can be slow

Find Empty Files in a Backup

Zero-byte files can be normal, or they can be failed writes.

find backup -type f -size 0 -print
Hosting Operations Can be slow

Find System Cron Files Fast

A job can be nowhere in your crontab and still run every night.

find /etc/cron.d /etc/cron.hourly /etc/cron.daily /etc/cron.weekly /etc/cron.monthly -maxdepth 1 -type f -print 2>/dev/null | sort
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.