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...
Thanks for your reply Andrew. So are you saying without the posix ACL
module, no unix permissions will be written on the destination at
all? So
essentially all files written out by rdiff-backup will have the
default
permissions as set by the umask?
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?
We have the posix ACL python module installed on both the source and
destination machines, rdiff-backup runs as root on the source and a
standard
user UID on the destination.
The troublesome files are usually ones with very restrictive
permissions on
the source. For example '/usr/bin/sudoedit' on one machine which is
owned by
root:root and has permissions 4111. It can be backed up fine, but when
rdiff-backup wants to do something with the backed up file on a
later run
(now running as a non-root user) it can't read the file and can't
force the
permissions as it is not running as root.