Back to commands

Hosting Operations

Read-only, can be slow

Check Whether Expected Build Outputs Exist

A deploy or packaging step cannot find files, and you need to verify the build output tree before debugging the deploy tool.

Command

find artifacts/dist -maxdepth 2 -type f | 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 assume files are correct just because they exist; inspect sizes and content as needed.

Expected output

A sorted manifest of files under artifacts/dist.

System impact

Read-only, can be slow. Nothing changes. The build output files are listed.

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

Recovery / rollback: no state is changed.

When to use it

Use when deploy, packaging, or static hosting steps complain about missing files.

When not to use it

Do not assume files are correct just because they exist; inspect sizes and content as needed.

next steps

Related commands

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

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

List Restore Points Before a Drill

A restore drill starts by proving which backups actually exist.

BACKUP_ROOT=/srv/backups/site && find "$BACKUP_ROOT" -maxdepth 2 -type f -name MANIFEST.txt -printf '%TY-%Tm-%Td %TH:%TM %h\n' | sort -r

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

Hosting Operations Can be slow

Find the Largest CI Artifacts

A bloated artifact can explain a slow or failed pipeline.

find artifacts -type f -printf '%s %p\n' | sort -nr | head -10

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.

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