1
0
Fork 0
mirror of https://github.com/borgbackup/borg.git synced 2024-12-23 16:26:29 +00:00

minor rewrite to make it less confusing (get rid of "Avoid to create a mixup") (#5490)

docs: permissions note rewritten to make it less confusing

Original wording was confusing "Avoid to create a mixup of users and permissions in your repository (or cache)." is not clear, what should be avoided?

Also implement some feedback of @jdchristensen.

Co-authored-by: Thomas Waldmann <tw@waldmann-edv.de>
This commit is contained in:
Mateusz Konieczny 2022-01-22 20:21:36 +01:00 committed by GitHub
parent 5edc773488
commit b4f54399d8
No known key found for this signature in database
GPG key ID: 4AEE18F83AFDEB23

View file

@ -71,26 +71,20 @@ Also helpful:
Important note about permissions Important note about permissions
-------------------------------- --------------------------------
Using root likely will be required if you want to backup files of other users To avoid permissions issues (in your borg repository or borg cache), **always
or the operating system. If you only back up your own files, you neither need access the repository using the same user account**.
nor want to use root.
Avoid to create a mixup of users and permissions in your repository (or cache). If you want to backup files of other users or the operating system, running
borg as root likely will be required (otherwise you'ld get `Permission denied`
errors).
If you only back up your own files, you neither need nor want to run borg as
root, just run it as your normal user.
This can easily happen if you run borg using different user accounts (e.g. your For a local repository just always use the same user to invoke borg.
non-privileged user and root) while accessing the same repo.
Of course, a non-root user will have no permission to work with the files
created by root (or another user) and borg operations will just fail with
`Permission denied`.
The easy way to avoid this is to always access the repo as the same user:
For a local repository just always invoke borg as same user.
For a remote repository: always use e.g. borg@remote_host. You can use this For a remote repository: always use e.g. borg@remote_host. You can use this
from different local users, the remote user accessing the repo will always be from different local users, the remote user running borg and accessing the
borg. repo will always be `borg`.
If you need to access a local repository from different users, you can use the If you need to access a local repository from different users, you can use the
same method by using ssh to borg@localhost. same method by using ssh to borg@localhost.