similar to: How do I restore using --fake-super?

On 08 Apr 2025, at 10:04, Paul Slootman via rsync <rsync at lists.samba.org> wrote: >> I have a backup that was created with --fake-super that I need to restore to a fresh partition on the same machine as the backup (source and destination on the same machine). >> >> The docs describe how --fake-super is used to make the backup, but none of the docs describe how you do

OK, my journey to make lab machines automagically install & update all desirable R packages is nearing an end! The only question I have now is this: How can I control where the system prints the *.Rout file that is created automatically when the R batch program runs. In "man R" I don't find any information about it. When the cron job runs "R_installAll.sh" (see

I upgraded from Fedora Core 4 to Fedora Core 5 and I find a lot of previously installed packages won't run because shared libraries or other system things have changed "out from under" the installed R libraries. I do not know for sure if the R version now from Fedora-Extras (2.2.1) is exactly the same one I was using in FC4. I see problems in many packages. Example, Hmisc: unable

I have released rsync version 3.3.0. This is a bug fix release, with the increased version bump being a delayed reaction to some of the recent larger changes that have happened. To see a summary of all the recent changes, visit this link: https://rsync.samba.org/ftp/rsync/NEWS#3.3.0 You can download the source tar file and its signature from here:

I have released rsync version 3.3.0. This is a bug fix release, with the increased version bump being a delayed reaction to some of the recent larger changes that have happened. To see a summary of all the recent changes, visit this link: https://rsync.samba.org/ftp/rsync/NEWS#3.3.0 You can download the source tar file and its signature from here:

Hello trusty rsync list, I'm excited about --fake-super as it will replace too much work with none at all. I have gotten it to work under linux and I have a fair grasp with what is happening there. I have a problem, though, and that is, in the long term, I'll need to archive my Linux systems not to a Linux box, but to a Solaris 10 box. I understand that Solaris does have extended

https://bugzilla.samba.org/show_bug.cgi?id=7108 Summary: --fake-super should be nestable Product: rsync Version: 3.1.0 Platform: All OS/Version: All Status: NEW Severity: enhancement Priority: P3 Component: core AssignedTo: wayned at samba.org ReportedBy: matt at mattmccutchen.net

https://bugzilla.samba.org/show_bug.cgi?id=7110 Summary: Symlink fake-super data is silently lost when sys_lsetxattr fails with EPERM Product: rsync Version: 3.1.0 Platform: All OS/Version: All Status: NEW Severity: major Priority: P3 Component: core AssignedTo: wayned at

https://bugzilla.samba.org/show_bug.cgi?id=7112 Summary: --fake-super should use default permissions for real files Product: rsync Version: 3.1.0 Platform: All OS/Version: All Status: NEW Severity: enhancement Priority: P3 Component: core AssignedTo: wayned at samba.org

I'm rsyncing files on system1 to its external HD. system2 is remote and pulls those files from the external HD. system2 does not have root privileges on system1 so I chown the files to pull. Can I somehow use --fake-super or something similar to save the original ownership info to ACLs? - Grant

Hey, I am experiencing a problem when excluding files that are not readable by the user on the source side. rsync version is 3.1.1. on debian jessy. Here is a "minimal" example: # preparation: $ mkdir -p source/subdir $ touch source/subdir/ignored_file $ sudo chown root:root source/subdir/ignored_file $ sudo chmod 600 source/subdir/ignored_file $ mkdir

ln -s real-file symlink file.itself is ./rsync.symlinks/file.itself, but you are trying to link ./file.itself (which presumably doesn't exist) to the real file. Since a symlink is just a pointer, it gets created, but doesn't point to any real file. Try: ln -s rsync.symlinks/file.itself . Joe On 10/11/2015 06:17 AM, Pavel Alexeev wrote: > Hi all. > > I long time discover

https://bugzilla.samba.org/show_bug.cgi?id=11558 Bug ID: 11558 Summary: rsync always try change owner and group of symlink in --fake-super mode Product: rsync Version: 3.1.2 Hardware: x64 OS: Linux Status: NEW Severity: normal Priority: P5 Component: core

Permissions don't require super. Any place where permissions can't be stored certainly can't handle xattrs either. So, I wouldn't expect --fake-super to affect --perms at all. On 3/12/20 12:46 PM, Dimitrios Apostolou via rsync wrote: > rsync --perms -M--fake-super src dst > > For me, this command means that rsync should save the original perms in the > xattr, and

I would expect that the sending rsync would only send the perms provided modified by the --chmod. I wouldn't expect the receiver to even know the other permissions. On 3/12/20 1:23 PM, Dimitrios Apostolou via rsync wrote: > Thank you for the feedback, I'm glad to see that different people see > the issue > differently. As a followup question, what would you expect this to do:

I don't believe it is possible. I think the misunderstanding stems from the fact that the permissions are even stored in the xattr. They don't need to be there but they may as well be. They don't take much space. The real question would be when rsync reads the file to restore it and the file perms are different than the ones in the xattr which set does it use? On 3/16/20 10:01 AM,

I am on rsync version 3.2.7 protocol version 31, currently on an Arch Linux. The following seems I would expect to copy the contents of 'a' to 'c', based on my understanding of the the advice of `man rsync`: ----- mkdir a b c touch a/hello rsync -M--fake-super -a a/ b/ rsync --super -M--fake-super -a b/ c/ ----- Instead I see 'c' unchanged, and a garbage directory

Hi all, I have a backup that was created with --fake-super that I need to restore to a fresh partition on the same machine as the backup (source and destination on the same machine). The docs describe how --fake-super is used to make the backup, but none of the docs describe how you do the reverse and restore. Google is hallucinating some nonsense, so that's a dead end. Can anyone confirm

On Tue 08 Apr 2025, Graham Leggett via rsync wrote: > > I have a backup that was created with --fake-super that I need to restore to a fresh partition on the same machine as the backup (source and destination on the same machine). > > The docs describe how --fake-super is used to make the backup, but none of the docs describe how you do the reverse and restore. The manpage says:

https://bugzilla.samba.org/show_bug.cgi?id=10496 Summary: --itemize-changes always reports xattr changes with --xattrs --fake-super Product: rsync Version: 3.1.1 Platform: All OS/Version: Linux Status: NEW Severity: normal Priority: P5 Component: core AssignedTo: wayned at