Bug or feature missing in rsync.

Bug or feature missing in rsync.

[Linda Walsh]

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

Re: Bug or feature missing in rsync.

[Lapo Luchini]

[-- Attachment #1: Type: text/plain, Size: 1444 bytes --]

Linda Walsh wrote:
> However the local rsync was build without the external attribute support.

Yes, configure fails to detect it, with the following error:

configure:8048: checking for __facl
configure:8048: gcc -std=gnu99 -o conftest.exe -O2 -pipe
-DHAVE_CONFIG_H -Wall -W   conftest.c -lpopt -liconv  >&5
/cygdrive/c/DOCUME~1/SSHD_S~1.000/LOCALS~1/Temp/cc0LUGb0.o:conftest.c:(.text+0x17):
undefined reference to `___facl'
collect2: ld returned 1 exit status

> 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?

Not a decision at all: it simply isn't detected as is and so far nobody
wrote a patch to have it working... (me included)

> 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.

What's "the NT list"?
Anyways, the reason is nothing more arcane than "configure doesn't
detect it".

> Should it be a reconfig and recompile?

No, more likely a "RTFM regarding facl support in Cygwin" +
"write a patch" + reconfig + recompile...

-- 
Lapo Luchini - http://lapo.it/

“We can factor the number 15 with quantum computers. We can also factor
the number 15 with a dog trained to bark three times.” (Robert Harley,
sci.crypt, 2001-12-05)


[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 898 bytes --]

Re: Bug or feature missing in rsync.

[Lapo Luchini]

[-- Attachment #1: Type: text/plain, Size: 1236 bytes --]

Lapo Luchini wrote:
> Linda Walsh wrote:
>> However the local rsync was build without the external attribute support.
> 
> Yes, configure fails to detect it, with the following error:
> 
> configure:8048: checking for __facl

No, sorry about the noise, that has nothing to do with xattrs, it's the
previous test; also __facl may not found, but _facl is found indeed.

The real reason is the following test:

  configure:8272: checking whether to support extended attributes
  configure:8321: result: No extended attribute support found

...well, judging from configure lines 8272-8321 it seems rsync xattr
support is only available in linux, darwin and freebsd.

So, yes, that isn't "activating a switch" but rater "write a feature",
which could be easy or difficult - I don't know enough about it right
now to be the judge of that; definitely needs some more RTFM regarding
xattrs on my side (and that needs time, which I have little on my hands,
right now).
As usual, the PTC principle applies there to have results faster.
http://www.cygwin.com/acronyms/#PTC

-- 
Lapo Luchini - http://lapo.it/

“There is no reason anyone would want a computer in their home.” (Ken
Olson, founder of DEC, 1977)


[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 898 bytes --]

Re: Bug or feature missing in rsync.

[Dave Korn]

Lapo Luchini wrote:

> The real reason is the following test:
> 
>   configure:8272: checking whether to support extended attributes
>   configure:8321: result: No extended attribute support found
> 
> ...well, judging from configure lines 8272-8321 it seems rsync xattr
> support is only available in linux, darwin and freebsd.
> 
> So, yes, that isn't "activating a switch" but rater "write a feature",
> which could be easy or difficult - I don't know enough about it right
> now to be the judge of that; definitely needs some more RTFM regarding
> xattrs on my side (and that needs time, which I have little on my hands,
> right now).
> As usual, the PTC principle applies there to have results faster.
> http://www.cygwin.com/acronyms/#PTC

  It appears that cygwin has the xattr functions implemented and exported:

> $ grep setxattr /gnu/winsup/src/winsup/cygwin/cygwin.din
> fsetxattr SIGFE
> lsetxattr SIGFE
> setxattr SIGFE

  So it could be as simple as using the existing linux support on cygwin too,
by doing something like:

$ diff -pu configure.in.orig configure.in
--- configure.in.orig   2009-09-16 13:10:53.125000000 +0100
+++ configure.in        2009-09-16 13:11:41.437500000 +0100
@@ -933,7 +933,7 @@ if test x"$enable_xattr_support" = x"no"
     AC_MSG_RESULT(no)
 else
     case "$host_os" in
-    *linux*)
+    *linux* | *cygwin*)
        AC_MSG_RESULT(Using Linux xattrs)
        AC_DEFINE(HAVE_LINUX_XATTRS, 1, [True if you have Linux xattrs])
        AC_DEFINE(SUPPORT_XATTRS, 1)

admin@ubik /usr/src/rsync/rsync-3.0.5

... followed of course by regenerating configure.sh.

  I haven't tested this (my cpu usage is already 100% and likely to stay that
way for the next day or two!), but maybe you'd like to give it a whirl?

    cheers,
      DaveK


--
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

Re: Bug or feature missing in rsync.

[Lapo Luchini]

Dave Korn wrote:
>   It appears that cygwin has the xattr functions implemented and exported:
> 
> ... followed of course by regenerating configure.sh.
> 
>   I haven't tested this (my cpu usage is already 100% and likely to stay that
> way for the next day or two!), but maybe you'd like to give it a whirl?

Of course I'd like to; I didn't hope it could be as easy as that. =)

-- 
Lapo Luchini - http://lapo.it/

“Don't dream it… be it!” (The Rocky Horror Picture Show)

--
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

Re: Bug or feature missing in rsync.

[Lapo Luchini]

[-- Attachment #1: Type: text/plain, Size: 1037 bytes --]

Lapo Luchini wrote:
> Dave Korn wrote:
>>   It appears that cygwin has the xattr functions implemented and exported
> 
> Of course I'd like to; I didn't hope it could be as easy as that. =)

Yes, it seems it was as easy as that.

% rsync-3.0.6-1/inst/usr/bin/rsync.exe --version
rsync  version 3.0.6  protocol version 30
Copyright (C) 1996-2009 by Andrew Tridgell, Wayne Davison, and others.
Web site: http://rsync.samba.org/
Capabilities:
    64-bit files, 64-bit inums, 32-bit timestamps, 64-bit long ints,
    socketpairs, hardlinks, symlinks, IPv6, batchfiles, inplace,
    append, ACLs, xattrs, iconv, symtimes

"make check" tests seems to have good results too, except the xattr one
is a SKIP.
Mhhh, that depends on a missing commandline "setfattr" utility.
But the package itself could be GTG anyways (it sure shouldn't be
"worse" than the current 3.0.5 one).

-- 
Lapo Luchini - http://lapo.it/

“There is no reason anyone would want a computer in their home.” (Ken
Olson, founder of DEC, 1977)


[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 898 bytes --]

Re: Bug or feature missing in rsync.

[Dave Korn]

Lapo Luchini wrote:
> Lapo Luchini wrote:
>> Dave Korn wrote:
>>>   It appears that cygwin has the xattr functions implemented and exported
>> Of course I'd like to; I didn't hope it could be as easy as that. =)
> 
> Yes, it seems it was as easy as that.

  Hmm, it may or may not be...

> % rsync-3.0.6-1/inst/usr/bin/rsync.exe --version
> rsync  version 3.0.6  protocol version 30
> Copyright (C) 1996-2009 by Andrew Tridgell, Wayne Davison, and others.
> Web site: http://rsync.samba.org/
> Capabilities:
>     64-bit files, 64-bit inums, 32-bit timestamps, 64-bit long ints,
>     socketpairs, hardlinks, symlinks, IPv6, batchfiles, inplace,
>     append, ACLs, xattrs, iconv, symtimes
> 
> "make check" tests seems to have good results too, except the xattr one
> is a SKIP.
> Mhhh, that depends on a missing commandline "setfattr" utility.

  I downloaded ftp://oss.sgi.com/projects/xfs/cmd_tars/attr_2.4.43-1.tar.gz
and found it builds OOTB, but my first attempt to use setfattr got me an error:

> $ ./setfattr/.libs/setfattr.exe -n bar -v baz foo
> setfattr: foo: Operation not supported

  Nor was getfattr capable of showing me the attributes I set in the windows
explorer file properties "summary" tab.  I'm taking a look through the strace
to see what's failing and why.  The code might need a little porting.

    cheers,
      DaveK



--
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

Re: Bug or feature missing in rsync.

[Dave Korn]

Dave Korn wrote:

>   I downloaded ftp://oss.sgi.com/projects/xfs/cmd_tars/attr_2.4.43-1.tar.gz
> and found it builds OOTB, but my first attempt to use setfattr got me an error:
> 
>> $ ./setfattr/.libs/setfattr.exe -n bar -v baz foo
>> setfattr: foo: Operation not supported
> 
>   Nor was getfattr capable of showing me the attributes I set in the windows
> explorer file properties "summary" tab.  

  Ah, looks like Cygwin only supports xattr on Samba filesystems.

    cheers,
      DaveK

--
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

Re: Bug or feature missing in rsync.

[Lapo Luchini]

Dave Korn wrote:
> Ah, looks like Cygwin only supports xattr on Samba filesystems.

Mhh, well okay, then maybe I can upload the new 3.0.6 release anyways,
announcing that the xattr feature is in testing (but the rest of the
release is really as good as the previous was).

-- 
Lapo Luchini - http://lapo.it/


--
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

Re: Bug or feature missing in rsync.

[Dave Korn]

Lapo Luchini wrote:
> Dave Korn wrote:
>> Ah, looks like Cygwin only supports xattr on Samba filesystems.
> 
> Mhh, well okay, then maybe I can upload the new 3.0.6 release anyways,
> announcing that the xattr feature is in testing (but the rest of the
> release is really as good as the previous was).

  Actually it turns out to be a bug; xattr should work fine on NTFS too, once
the next version of the cygwin dll is released.

    cheers,
      DaveK


--
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

Re: Bug or feature missing in rsync.

[Vincent R.]

Hi,

After having started some debate about cygdrive prefix (it was not my
goal) I think I have another 
dilemna ;-)
I want to try to compile cegcc-4.4.0 (gcc targetting windows ce) with a
mingw compiler but I don't 
know which one to choose.
As always with open source software I can use :

a) mingw(4.4.0) compiler from mingw project
b) mingw32(4.4.1) compiler from mingw64(maybe renamed in monika) project
c) mingw(3.4.4) from cygwin

When choosing option c) how do you select mingw compiler ? I found some
old post but don't 
know if it's still valid.
Do I need to pass some CFLAGS ?

Dave, by the way when will it be possible to play with your
cygwin-mingw-4.3x compiler

Thanks


--
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

mingw question : Post repetita

[Vincent R.]

Hi,

After having started some debate about cygdrive prefix (it was not my
goal) I think I have another 
dilemna ;-)
I want to try to compile cegcc-4.4.0 (gcc targetting windows ce) with a
mingw compiler but I don't 
know which one to choose.
As always with open source software I can use :

a) mingw(4.4.0) compiler from mingw project
b) mingw32(4.4.1) compiler from mingw64(maybe renamed in monika) project
c) mingw(3.4.4) from cygwin

When choosing option c) how do you select mingw compiler ? I found some
old post but don't 
know if it's still valid.
Do I need to pass some CFLAGS ?

Dave, by the way when will it be possible to play with your
cygwin-mingw-4.3x compiler

Thanks

PS : I am posting again because I hijacked another thread. Sorry about
that.


--
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

Re: mingw question : Post repetita

[Dave Korn]

Vincent R. wrote:

> I want to try to compile cegcc-4.4.0 (gcc targetting windows ce) with a
> mingw compiler but I don't know which one to choose.
> As always with open source software I can use :
> 
> a) mingw(4.4.0) compiler from mingw project
> b) mingw32(4.4.1) compiler from mingw64(maybe renamed in monika) project
> c) mingw(3.4.4) from cygwin
> 
> When choosing option c) how do you select mingw compiler ? I found some
> old post but don't know if it's still valid.

  You need to make sure the compiler is invoked with "-mno-cygwin".  And that
gcc-3 is the default set in your alternatives configuration (which it should
be unless you've manually changed it).

> Do I need to pass some CFLAGS ?

  Well, that depends on how your makefile system works, but CFLAGS is the
standard way to pass an option through to the compiler.  However you may have
problems using a compiler that old with recent code; hard to predict.

> Dave, by the way when will it be possible to play with your
> cygwin-mingw-4.3x compiler

  I'm running the final full testsuite.  Started Monday evening, exploded
horribly late last night somewhere in the fortran compiler tests, needs
restarting from where it left off, will take several more days to run.
Assuming the results are then good (they have all been so far), I'd update the
README and upload it.  I know I've said "coming soon" before, but a whole
bunch of bugs cropped up that needed fixing.  I think they're fixed now, but
can't be certain until I finish the test cycle.

> PS : I am posting again because I hijacked another thread. Sorry about
> that.

  But it's no use replying-to your first hijack post to try and start a new
thread, it just ended up in the same thread anyway!

    cheers,
      DaveK



--
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

Re: Bug or feature missing in rsync.

[Corinna Vinschen]

On Sep 16 15:41, Dave Korn wrote:
> Dave Korn wrote:
> 
> >   I downloaded ftp://oss.sgi.com/projects/xfs/cmd_tars/attr_2.4.43-1.tar.gz
> > and found it builds OOTB, but my first attempt to use setfattr got me an error:
> > 
> >> $ ./setfattr/.libs/setfattr.exe -n bar -v baz foo
> >> setfattr: foo: Operation not supported
> > 
> >   Nor was getfattr capable of showing me the attributes I set in the windows
> > explorer file properties "summary" tab.  
> 
>   Ah, looks like Cygwin only supports xattr on Samba filesystems.

I don't know if that has shown up already, so... that's a bug which has
been fixed by cgf (thanks!) in the meantime.


Corinna

-- 
Corinna Vinschen                  Please, send mails regarding Cygwin to
Cygwin Project Co-Leader          cygwin AT cygwin DOT com
Red Hat

--
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

Re: Bug or feature missing in rsync.

[Linda Walsh]

Lapo Luchini wrote:
> Lapo Luchini wrote:
>> Dave Korn wrote:
>>>   It appears that cygwin has the xattr functions implemented and exported
>> Of course I'd like to; I didn't hope it could be as easy as that. =)
> 
> Yes, it seems it was as easy as that.
> 
> % rsync-3.0.6-1/inst/usr/bin/rsync.exe --version
> rsync  version 3.0.6  protocol version 30
> Copyright (C) 1996-2009 by Andrew Tridgell, Wayne Davison, and others.
> Web site: http://rsync.samba.org/
> Capabilities:
>     64-bit files, 64-bit inums, 32-bit timestamps, 64-bit long ints,
>     socketpairs, hardlinks, symlinks, IPv6, batchfiles, inplace,
>     append, ACLs, xattrs, iconv, symtimes
> 
> "make check" tests seems to have good results too, except the xattr one
> is a SKIP.
> Mhhh, that depends on a missing commandline "setfattr" utility.
> But the package itself could be GTG anyways (it sure shouldn't be
> "worse" than the current 3.0.5 one).
> 
----
	On my linux box there's an 'xattr' command to set attribs on xfs files systems
and is compatible with the Irix command of the same name.

But if rsync makes the extended attr calls internally, the xattr call shouldn't be 
explicitly needed.

Samba has to be set to pass through the xattr calls to the underlying file system
on each share "ea support = yes".

According to the docs it will enable storing of what it calls "OS/2" style
extended attribs by using the native file systems extended attribute system.

So 'ideally', *cough*, it should just work.

I can always check to see if extended attr's show up on my linux file system.
Was writing a script to run xattr over my files -- it's a primitive util
that doesn't support wildcards or recursion.


--
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