All, thanks!
Nope, I wouldn't think of changing anything inside a backup repo. Since it
seems to work with the right permissions and ownership in repos, my only
real question is whether the 777 on the owned-by-me partition and the 755
on the owned-by-me backups directory would get me in trouble
Hi,
basically the difference lies mainly in what you can read (as root everything)
not so much in what is written, because, as Patrik wrote, the access rights are
saved as metadata even if the user can't create the file as read.
I would use a normal user to save their own home, root for
To my knowledge permission and ownership may be reflected to the target
destination but extra care need to be taken care of to make it happen. Man
page explains most of it.
Otherwise, Most of the time permission are not reflected to the target
destination and are simply stored in metadata. Then
Do the permissions and owners listed near the end seem reasonable?
Looking at it again this morning, I guess they do.
I guess I need to run this script as root, because I'm backing up files
from two different users.
Bill
On Sun, Nov 7, 2021 at 1:11 AM Dominic Raferd
wrote:
> On 06/11/2021
On 06/11/2021 18:45, Bill Harris wrote:
I've been using rdiff-backup for 10+ years...
What is the problem?
I've been using rdiff-backup for 10+ years. I developed a simple bash
script that did what I wanted, and then I just ran it. My OS is and has
been Debian Stable.
My script
- checks to make sure I'm running as root (I forget why I did that 10+
years ago)
- for each of 4 rdiff-backup
