public inbox for cygwin@cygwin.com
 help / color / mirror / Atom feed
From: Linda Walsh <cygwin@tlinx.org>
To: "cygwin@cygwin.com" <cygwin@cygwin.com>
Subject: Bug or feature missing in rsync.
Date: Tue, 08 Sep 2009 10:28:00 -0000	[thread overview]
Message-ID: <4AA61819.4030501@tlinx.org> (raw)


I'm trying to copy NTFS file permisions to a SMB share with ACLS and extended
attributes on top of XFS.

However the local rsync was build without the external attribute support.

I am not sure why -- I was going to use teh --fake-super to store the NT ACL's
on the target file system, but due to the crippled rsync on cygwin, it doesn't
work.  

Is this an oversite or is the cygwin version just that far behind the curve?

There's even extended attributes on NT.  So I can't see why the decision was
made not to include such support from the beginning...

Reasoning on this?

Can a new version be compiled with these features in?  If I am rsyncing to
my Domain controller, I'd almost think it should be able to store the ACLS
in a semi-native format (not that they'd mean anything on linux, but
for a WinNT client, they should look the same as local ACLS, no?

Is this fixable?

I asked about it on the NT list, and I was asked why rsync wasn't using
getextattr/setextattr under cygwin, as they said they were present.

I had no answer...

Should it be a reconfig and recompile?

Thanks...
-linda
(who hasn't gotten a backup of her sys for some time due to NTBACKUP crashing
at the very END of the bakup (as it is closing the file) -- when it probmptly
removes the 80GB file that took  6-8 hours to create.  Lovely.




--
Problem reports:       http://cygwin.com/problems.html
FAQ:                   http://cygwin.com/faq/
Documentation:         http://cygwin.com/docs.html
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple

             reply	other threads:[~2009-09-08 10:28 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-09-08 10:28 Linda Walsh [this message]
2009-09-16  9:03 ` Lapo Luchini
2009-09-16  9:24   ` Lapo Luchini
2009-09-16 11:59     ` Dave Korn
2009-09-16 13:33       ` Lapo Luchini
2009-09-16 14:00         ` Lapo Luchini
2009-09-16 14:23           ` Dave Korn
2009-09-16 14:26             ` Dave Korn
2009-09-17  4:48               ` Lapo Luchini
2009-09-17 10:27                 ` Dave Korn
2009-09-17 12:08                   ` Vincent R.
2009-09-17 13:23                     ` mingw question : Post repetita Vincent R.
2009-09-17 13:39                       ` Dave Korn
2009-09-21 14:58               ` Bug or feature missing in rsync Corinna Vinschen
2009-09-16 18:52           ` Linda Walsh

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=4AA61819.4030501@tlinx.org \
    --to=cygwin@tlinx.org \
    --cc=cygwin@cygwin.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).