****This is an edited version of a previous post****
Hi Andrew, Thanks for replying. I have the latest rdiffbackup (1.0.5) and librsync (0.9.7). Any ideas? It seems to be that rdiff or python is deciding to set some unusual permissions. To give you more info, I just found out that this 'None' user is a red herring. The real symptom is the following: I can manually create files in the same cygwin session (e.g. 'touch file.txt') and they inherit the permissions I would expect. However, when I attempt a backup in a folder with normal security, the backup fails with the mentioned error. When I inspect the folder, I find that the Windows permissions have changed; now even though the destination folder is still owned by my user, no one (including that user) has any read or write permissions when I look at the Windows folder security. Cygwin tells me the folder looks like this: d---------+ 2 stan None 4096 Jul 17 03:04 backup but this isn't that helpful because even my accessible folders display these same unix ACLs. Thanks, Stan +---------------------------------------------------------------------- |This was sent by [EMAIL PROTECTED] via Backup Central. |Forward SPAM to [EMAIL PROTECTED] +---------------------------------------------------------------------- _______________________________________________ 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
