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 everything else. And foremost I wouldn't change the approach once started! And not change the access rights directly in a backup repository.
Hope this helps, Eric On 7 November 2021 16:35:41 CET, Patrik Dufresne <pat...@ikus-soft.com> wrote: >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 everything is owned by >the users running the script and 0700 for permissions. > >Running the script as root might help. But would need to look at man page >to make sure. > >On Sun., Nov. 7, 2021, 10:19 a.m. Bill Harris, < >bill_har...@facilitatedsystems.com> wrote: > >> 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 <domi...@timedicer.co.uk> >> wrote: >> >> > On 06/11/2021 18:45, Bill Harris wrote: >> > > I've been using rdiff-backup for 10+ years... >> > What is the problem? >> > >> > >>
