satwell
/
borgmatic
forked from borgmatic-collective/borgmatic
1
0
Fork 0
Code Issues Pull Requests Projects Releases Wiki Activity

Add mention of sudo's "secure_path" option in borgmatic installation documentation (#513).

This commit is contained in:
Dan Helfman 2022-04-23 14:29:55 -07:00
parent 0e6b425ac5
commit d045eb55ac
2 changed files with 6 additions and 0 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

1
NEWS
View File

@ -6,6 +6,7 @@
once for each configured repository instead of once per configuration file. Additionally, the
"repositories" interpolated variable has been changed to "repository", containing the path to the
current repository for the hook.
* #513: Add mention of sudo's "secure_path" option in borgmatic installation documentation.
* #515: Fix "borgmatic borg key ..." to pass parameters to Borg in correct order.
* #516: Fix handling of TERM signal to exit borgmatic, not just forward the signal to Borg.
* #517: Fix borgmatic exit code (so it's zero) when initial Borg calls fail but later retries

5
docs/how-to/set-up-backups.md
View File

@ -51,6 +51,11 @@ sudo borgmatic --version
If borgmatic is properly installed, that should output your borgmatic version.
As an alternative to adding the path to `~/.bashrc` file, if you're using sudo
to run borgmatic, you can configure [sudo's
`secure_path` option](https://man.archlinux.org/man/sudoers.5) to include
borgmatic's path.
### Global install option