Skip to content

Commit c9fb1d1

Browse files
committed
fix: path
1 parent 168ddb5 commit c9fb1d1

File tree

1 file changed

+2
-2
lines changed

1 file changed

+2
-2
lines changed

_posts/2023-07-02-using-prune-to-manage-archives.md

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -27,7 +27,7 @@ rm prune prune-linux-x64.tar.gz
2727

2828
Once it's installed, you should be able to run prune simply by typing in `prune`, **but don't**. Prune is designed to delete things, and you should always run it with `--dry-run` and `--verbose` until you're certain what will be pruned.
2929

30-
![prune help](../assets/img/using-prune-to-manage-archives/prune-help.png)
30+
![prune help](/assets/img/using-prune-to-manage-archives/prune-help.png)
3131

3232
To use prune, you will need to provide a pruning path and some retention value. Keep in mind prune is not recursive, so it will only purge files directly in the path you give. Prune also uses last modified date, not created date to evaluate what files to keep and prune. This allows for incremental backups with updates to be properly evaluated. You must specify some level of retention for prune to run.
3333

@@ -36,7 +36,7 @@ prune --path /home/patrick/test/ --keep-last 10 --dry-run --verbose
3636
```
3737
Example output:
3838

39-
![prune example output](../assets/img/using-prune-to-manage-archives/prune-example-output.png)
39+
![prune example output](/assets/img/using-prune-to-manage-archives/prune-example-output.png)
4040

4141
You can also provide more file filtering using `--prefix` and `--ext`.
4242

0 commit comments

Comments
 (0)