Shorten the README's opening sentence for --prune
Adding .partial objects made the first sentence of the --prune bullet about 70 words long, chaining three cleanup steps with "and ..., and". It now says the flag deletes from the destination store what prune deletes there; the prune section lists what that is. Model: opus-5-5
This commit is contained in:
1 parent
18961fa52f
commit
332c2d30a2
1 file changed
+13
-17
@@ -340,23 +340,19 @@ In such a config, an unknown key or a value of the wrong type is refused.
|
|||||||
error that explains how to fix it
|
error that explains how to fix it
|
||||||
- `--cron`: Silent on total success; warnings and errors are still printed (for
|
- `--cron`: Silent on total success; warnings and errors are still printed (for
|
||||||
crontab)
|
crontab)
|
||||||
- `--prune`: After backup, drop older snapshots of each backed-up name, remove
|
- `--prune`: After backup, drop older snapshots of each backed-up name, then
|
||||||
orphaned blobs older than `prune_grace_period` from remote storage, and delete
|
delete from the destination store what `prune` deletes there. By default keeps
|
||||||
each directory under `metadata/` that has no `manifest.json.zst` once every
|
only the latest snapshot per name; use `--keep-newer-than` for a rolling
|
||||||
object in it is older than `prune_grace_period` and its snapshot is not in the
|
window. When `--skip-errors` skipped a file or directory it could not read or
|
||||||
local index, and delete each `.partial` object older than
|
list, the prune does not run and every older snapshot is kept, since one of
|
||||||
`prune_grace_period`, as `prune` does. By default keeps only the latest
|
them may be the only one that holds what was skipped; the command says so and
|
||||||
snapshot per name; use `--keep-newer-than` for a rolling window. When
|
exits non-zero. When the backup found nothing in a configured path, as in the
|
||||||
`--skip-errors` skipped a file or directory it could not read or list, the
|
mount point of a volume that is not mounted, the prune does not run either:
|
||||||
prune does not run and every older snapshot is kept, since one of them may be
|
every older snapshot is kept, and the command names the path and exits
|
||||||
the only one that holds what was skipped; the command says so and exits
|
non-zero, on every run until the path holds something again. Take a path that
|
||||||
non-zero. When the backup found nothing in a configured path, as in the mount
|
is empty on purpose out of the config, or remove the older snapshots by hand
|
||||||
point of a volume that is not mounted, the prune does not run either: every
|
with `snapshot purge`. When an earlier snapshot of the same name in the local
|
||||||
older snapshot is kept, and the command names the path and exits non-zero, on
|
index found a volume mounted at or below a configured path (a directory on a
|
||||||
every run until the path holds something again. Take a path that is empty on
|
|
||||||
purpose out of the config, or remove the older snapshots by hand with
|
|
||||||
`snapshot purge`. When an earlier snapshot of the same name in the local index
|
|
||||||
found a volume mounted at or below a configured path (a directory on a
|
|
||||||
different filesystem from its parent, with an entry in it that the backup does
|
different filesystem from its parent, with an entry in it that the backup does
|
||||||
not exclude) and this backup does not, the prune does not run either: every
|
not exclude) and this backup does not, the prune does not run either: every
|
||||||
older snapshot is kept, and the command names the directory and exits
|
older snapshot is kept, and the command names the directory and exits
|
||||||
|
|||||||
Reference in new issue
Block a user