Andrew Price wrote: > On 09/01/07 13:41, Andrew Ferguson wrote: >> From a quick glance at the source (I may have missed something obvious), >> the failure to open restore.log for writing doesn't look fatal. > You could be right, from the trace below it looks like some kind of > chmod problem, sorry if I was misleading. > >> Do you have a traceback of a failed rdiff-backup restore from read-only >> media that we could take a look at? > > Sure, it's a bit big so I uploaded the entire trace to > http://andrewprice.me.uk/dropoff/rdiff-backup.log.txt
Well, for starters, the whole branch of code its failing in is only called when you run rdiff-backup as a normal user. Try running the restore as root and see what happens. If it fails again, send us the new traceback. What's going on is that rdiff-backup is preemptively trying to give your user access to all of the mirror's files so that it doesn't run into permission errors later on. Andrew -- Andrew Ferguson - [EMAIL PROTECTED] _______________________________________________ rdiff-backup-users mailing list at rdiff-backup-users@nongnu.org http://lists.nongnu.org/mailman/listinfo/rdiff-backup-users Wiki URL: http://rdiff-backup.solutionsfirst.com.au/index.php/RdiffBackupWiki
