On Jul 22, 2008, at 1:05 AM, stanlin wrote:
One additional data point, where hopefully I'm giving back to this
community: in my humble suspicions, it may be that Cygwin+Vista is
somewhat broken, because the ACLs on all my files are all zeroed out
on Cygwin and don't reflect what I'm in reality able to do with
them. I referenced this posting:
If your understanding is the same, then it may be worthwhile to
release note this Vista problem for the upcoming build. While I wish
I could go back to XP as a workaround, it would be a drastic move.
If you can think of a workaround here as well I would greatly
appreciate it... I didnt see anything in the man pages about
overriding permissions during backup creation.
Glad to here things are (almost) working for you. Here are some more
things to think about:
- Rdiff-backup now builds natively on Windows. That is, if you have
native Windows python (and possibly py2exe as well), then you don't
need Cygwin to run it. In the rdiff-backup source, the setup.py file
can be run as "setup.py py2exe --single-file" ... search the recent
mailing list archives for native Windows and posts from Josh Nisly or
Fred Gansevles. If you're interested in going that route, start
another thread and one of those guys should be able to help you.
- It looks like the Cygwin people have heard about it and believe it
can be corrected by the user:
There's a good thread about these things on the official Cygwin list,
I suggest reading the whole thread, which starts here:
Another user suggests making sure Cygwin is run as an administrator:
- Lastly, since I know at least Josh is running rdiff-backup under
Windows XP -- what version of Vista are you using? Cygwin version? If
you get into trouble, I will need that information in order to create
a virtual machine to try to recreate your problem.
rdiff-backup-users mailing list at rdiff-backup-users@xxxxxxxxxx
Wiki URL: http://rdiff-backup.solutionsfirst.com.au/index.php/RdiffBackupWiki