[Rdiff-backup-bugs] [bug #29796] Windows ACLs don't save or restore the "inherit" flag.

[anonymous]

Follow-up Comment #2, bug #29796 (project rdiff-backup):

My mail adress because I did not sign up in this service: mail [AT] dkriesel
[DOT] com.

I second that rdiff backup 1.2.8 has its difficulties with file permissions
using windows server systems. However, I think we are only talking about a
single aspect of the bug here.

In my setup, the target directory tree of the rdiff transmission is set to
propagate inheritable permissions (which is common in backuping different
servers to a central backup storage system: each single backup source gets its
own directory tree which inherits its ACLs from its root). Such setups are
most easy to handle (even between to windows machines, like in my case),
because one doesn't want to transmit any permissions, inheritances or ACLs at
all.

Now sometimes (has to do with deleting and rebuilding files as far as I know,
not sure) rdiff messes up the ACLs of single files: It not only disables the
inheritance propagation flag that originally has been there, but also messes
ob the ACL dataset itself, adding the user group "none". This eventually
causes inconsistencies between the main data and the reverse deltas, because
during the next run rdiff won't be able to delete that single file whose ACL
was messed up if neccessary.

Long story short: Your rdiff repository gets messed up. So, how do I make
sure Rdiff itself doesn't touch anything related to the file permissions in a
target windows system? For me, the bug does not neccessarily have to be
resolved, I will be perfectly fine if maybe someone tells me that I oversaw
some flag that prevents Rdiff from touching any ACLs/inheritances/etc.

    _______________________________________________________

Reply to this item at:

  <http://savannah.nongnu.org/bugs/?29796>

_______________________________________________
  Nachricht geschickt von/durch Savannah
  http://savannah.nongnu.org/