Skip to main content

Output paths

All output lives under one data root. Which root depends on how you installed the tool, and both can be overridden.

Layout​

$DATA_HOME/
├── logs/
│ ├── cleanup-<YYYY-MM-DD_HHMMSS>.log # one per session
│ └── cron.log # appended by the weekly cron
├── reports/
│ ├── report-<YYYY-MM-DD_HHMMSS>.json # guided walkthrough record, unless disabled
│ ├── report-<YYYY-MM-DD_HHMMSS>.md # created by --export md
│ └── report-<YYYY-MM-DD_HHMMSS>.html # created by --export html
└── feedback/
├── debug-bundle-<YYYY-MM-DD_HHMMSS>.tar.gz # created by --debug-bundle
└── crash-<YYYY-MM-DD_HHMMSS>.tar.gz # created automatically on a crash

Per-install defaults​

Installed via$DATA_HOME
npx linux-cleanup~/.linux-cleanup/
npm install -g linux-cleanup~/.linux-cleanup/
git cloneThe clone directory itself

The difference is deliberate. npx runs the package from a temporary npm cache directory that gets evicted, so writing output there would lose it; ~/.linux-cleanup/ persists across runs. A clone is already a permanent location, so output stays beside the source.

Override either with LINUX_CLEANUP_DATA_HOME, or the log and record directories individually.

Retention​

PathAuto-cleanedNotes
logs/cleanup-*.logOnly with --cleanup-logsThat flag deletes this run's log at finish. Past logs stay
logs/cron.logNeverNever rotated. Rotate it yourself if it grows
reports/*.jsonNeverThe durable audit trail
reports/*.md, *.htmlNeverCreated on demand, removed on demand
feedback/*.tar.gzNeverYou decide when they are no longer needed

--cleanup-logs is the only automatic deletion the tool performs on its own output, and it only ever touches .log files.

Size and retention​

Log and bundle size depends on the paths and events in a run. Inspect what has accumulated before deleting old records. To thin older files deliberately:

find ~/.linux-cleanup/logs/ -name 'cleanup-*.log' -mtime +90 -delete
find ~/.linux-cleanup/reports/ -name 'report-*' -mtime +90 -delete

Rotating the cron log:

mv ~/.linux-cleanup/logs/cron.log ~/.linux-cleanup/logs/cron.log.old
touch ~/.linux-cleanup/logs/cron.log

Permissions​

Files are owned by the invoking user. Inspect their effective modes with stat on your machine; the tool's configured directory modes and the process umask both matter. Avoid sharing a log or bundle without reading it first.

What these files contain​

Logs and bundles contain your paths

A session log names every path touched, which means it contains directory names from your machine — project names, and sometimes filenames from ~/Downloads.

That is local-only and never transmitted, but review a bundle before emailing it:

tar -tzf ~/.linux-cleanup/feedback/debug-bundle-*.tar.gz

See Send a bug report.

Nothing here contains file contents — only paths, sizes and timestamps. These are records of what happened, not copies of what was deleted. See Recovery.

Next​