From d045eb55acad7b9033c16fa4219c3d30fafca8ec Mon Sep 17 00:00:00 2001 From: Dan Helfman Date: Sat, 23 Apr 2022 14:29:55 -0700 Subject: [PATCH] Add mention of sudo's "secure_path" option in borgmatic installation documentation (#513). --- NEWS | 1 + docs/how-to/set-up-backups.md | 5 +++++ 2 files changed, 6 insertions(+) diff --git a/NEWS b/NEWS index 5105226..c943096 100644 --- a/NEWS +++ b/NEWS @@ -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 diff --git a/docs/how-to/set-up-backups.md b/docs/how-to/set-up-backups.md index c58c558..b929771 100644 --- a/docs/how-to/set-up-backups.md +++ b/docs/how-to/set-up-backups.md @@ -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