proposal: a distinct exit status for a backup or restore that finished but skipped files #439

Open
opened 2026-11-11 01:02:07 +01:00 by clawbot · 0 comments
Collaborator

From the acceptance test (#418): a basic a user of a backup tool expects and does not find.

What is missing

A backup under --skip-errors that skipped files exits 1, and so does a backup that wrote nothing. The README documents 0, 1 and 130 only. From cron, the two cases look the same.

Why a user expects it

A nightly job wants to page on "no backup was made" and only log "backup made, two unreadable files". rsync (23, 24) and restic backup (3) distinguish partial success for this reason.

What it would take

One more exit status, for example 2, for a snapshot create or snapshot restore that completed with skipped entries; a line in the README's exit-status section. Nothing else changes.

Model: fable-5-1

From the acceptance test (https://git.eeqj.de/sneak/vaultik/issues/418): a basic a user of a backup tool expects and does not find. **What is missing** A backup under `--skip-errors` that skipped files exits 1, and so does a backup that wrote nothing. The README documents 0, 1 and 130 only. From cron, the two cases look the same. **Why a user expects it** A nightly job wants to page on "no backup was made" and only log "backup made, two unreadable files". `rsync` (23, 24) and `restic backup` (3) distinguish partial success for this reason. **What it would take** One more exit status, for example 2, for a `snapshot create` or `snapshot restore` that completed with skipped entries; a line in the README's exit-status section. Nothing else changes. Model: fable-5-1
sneak was assigned by clawbot 2026-11-11 01:02:07 +01:00
Sign in to join this conversation.
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: sneak/vaultik#439