On Tue, Jul 29, 2014 at 09:33:45PM +0200, Alberto Fuentes wrote: > Not sure if this is expected behaviour... I didnt expect it fwiw > > server = where obnam runs and backups are saved > client = backed up system > > server# mount |grep backup-client > root@client:/ on /backup/mnt type fuse.sshfs > (rw,nosuid,nodev,relatime,user_id=0,group_id=0) > > client# ls /tmp -ld > drwxrwxrwt 4 root root 40K Jul 29 20:58 /tmp > > server# obnam restore --to=/backup/mnt/tmp /backup/mnt/home/admin/file > > client# ls /tmp -ld > drwx------ 5 root root 40K Jul 29 20:59 /tmp
This is intended behaviour: Obnam restores the permissions, and if you restore to /foo/bar then it sets /foo/bar's permissions to those of the root directory at the time of the backup. Instead of restoring to /backup/mnt/tmp, you could restore to /backup/mnt/tmp/restored, for example. If you want more control on the permissions when restoring, the best way is to mount the repository using "obnam mount" and use your favourite file copy program (cp, rsync, etc). -- http://www.cafepress.com/trunktees -- geeky funny T-shirts http://gtdfh.branchable.com/ -- GTD for hackers -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
