Re: [rdiff-backup-users] Re: Permission denied on file in backup repository

[Andrew Ferguson]

On Jun 11, 2008, at 12:50 AM, Oliver Hookins wrote:

> Hi,
>
> some more on this issue which we still get a LOT of problems with.  
> It seems
> nobody really cares about this issue, since nobody has replied.
>
> When we get permission denied on files that have restrictive  
> permissions on
> the source due to performing the backup as a non-root user on the
> destination, if there was an option to not store permissions  
> natively this
> could fix the problem.
>
> I notice 1.1.15 has a "--no-acls" option which completely prevents  
> backing
> up ACLs. Would it be possible to add a "--no-native-acls" option  
> which only
> stores permissions in the meta-data? It would be supremely useful...

Oliver,

If you're sure that the problem is due to ACLs being stored on the  
destination, then why don't you remove the posix ACL python module on  
the destination? That would prevent rdiff-backup from writing them...

Also, you will need to provide more details on your setup  
(specifically the UID of rdiff-backup's process on both ends, ACL  
support, etc.) and the troublesome file(s) -- what are their unix  
permissions? ACL entries?

Regarding a "--no-write-acls" option: That would certainly be possible  
as there is already a 'acls_write' global variable which presumably  
would lead to such behavior (it would need to be tested as well), but  
it currently gets set destructively by the fs_abilities checks.  
Somebody would need to write a patch to make the update_triple()  
function do a better job at not over-writing preset global variables  
(instead of the current special case for the _active ones, like  
eas_active, acls_active, etc.)


Andrew