Dear Ben,
Does it use the Mac OS X specific command /usr/sbin/fsaclctl command?
If that is the case it would fail as the OS probably stores the ACL
enabled status at the root of the volume.
I tested it with python and manually and it works with all the
folders/ files within the ACL enabled volumes as expected! Given
this, I do not understand why rdiff-backup should bail out as it is
python based and uses pylibacl.
With many thanks.
Best regards,
Murali.
On 31 Oct 2005, at 02:21 am, Ben Escoto wrote:
Murali Vadivelu <[EMAIL PROTECTED]>
wrote the following on Sun, 30 Oct 2005 17:16:18 +0000
Could this be the cause? - Is rdiff-backup testing for acl ability
at the source and destination directory instead of the respective
volume root?
Sun Oct 30 16:10:09 2005 ACLs not supported by filesystem at /
Users/
muralikv/Desktop
Yes, if you are trying to back up /Users/muralikv/Desktop it will test
that very directory. If that test fails and you say --never-drop-acls
then it just exits with a fatal error.
--
Ben Escoto
_______________________________________________
rdiff-backup-users mailing list at [email protected]
http://lists.nongnu.org/mailman/listinfo/rdiff-backup-users
Wiki URL: http://rdiff-backup.solutionsfirst.com.au/index.php/RdiffBackupWiki