rdiff-backup-users
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

[rdiff-backup-users] Permission denied errors on files that originally h


From: Oliver Hookins
Subject: [rdiff-backup-users] Permission denied errors on files that originally have no user
Date: Fri, 25 Jan 2008 16:38:09 +1100
User-agent: Mutt/1.5.15+20070412 (2007-04-11)

permissions
Reply-To: 
X-Mailer: anchor v0.0
X-No-CC: Please respect the setting of my Mail-Followup-To header

Hi,

we're backing up some machines that have files with no read or write
permissions for the user, e.g. /usr/bin/sudoedit which has 4111 permissions,
giving only setuid execute to all.

When this file is backed up, the permissions remain in the backup
repository, but then the backup user on the next run can't access the file
for reads or writes, which causes rdiff-backup to bail out with an error
similar to the following:

Crashing on IOError: [Errno 13] Permission denied: 'backup/usr/bin/sudoedit'

Is there any way around this? Given this sort of situation can all to easily
arise, is it possible to drop all manner of native permissions storage in
the destination repo, and have it all stored in metadata?

-- 
Regards,
Oliver Hookins
Anchor Systems




reply via email to

[Prev in Thread] Current Thread [Next in Thread]