On Sun, Oct 25, 2009 at 6:26 PM, Carlos Carvalho wrote:
> All files are new. What I find strange is that I'd expect the transfered
> bytes to be somewhat larger than the file sizes
>
Yeah, there are two problems. One was that the %b modifier requires
late-logging (after the transfer finishes), a
I've just got the log lines below. The first line shows the format
spec that prints each column:
%'b %'l %f
0 18,760 f1
0 11,193 f2
32,768 2,186 f3
3,128,368 3,453,856 f4
13,680 11,786 f5
32,768 6,288 f
On Fri, Oct 23, 2009 at 10:36 AM, Matt McCutchen wrote:
> On Fri, 2009-10-23 at 11:31 +0200, Paul Slootman wrote:
>> On Fri 23 Oct 2009, Matt McCutchen wrote:
>> > On Fri, 2009-10-23 at 09:15 +0200, Riccardo Iaconelli wrote:
>> > >
>> > > [r...@popper linksys]# rsync -avz --hard-links test/ test2/
I don't know, I was just theoretically guessing.
I don't have a computer on 10.6 so I'm just fine with rsync :)
Le 25 oct. 09 à 18:36, Robert DuToit a écrit :
Hi Vitorio,
Yes -I kind of figured default was that now. What would be the way
to get i386 back:
would
./configure -arch i386 -a
Wayne Davison (way...@samba.org) wrote on 24 October 2009 15:32:
>On Fri, Oct 23, 2009 at 2:41 PM, Carlos Carvalho wrote:
>
>> The first is that when running with --files-from and -ii unmodified
>> files are not put in the log.
>
>
>That is not a logging issue, but rather an early-terminatio
Hi Vitorio,
Yes -I kind of figured default was that now. What would be the way to
get i386 back:
would
./configure -arch i386 -arch x86_64
work?
Rob
On Oct 25, 2009, at 1:30 PM, Mac User FR wrote:
For me this is a problem of gcc config on X.6.
It's targetting x64 by default instead o
For me this is a problem of gcc config on X.6.
It's targetting x64 by default instead of x86.
Cheers,
Vitorio
Le 25 oct. 09 à 18:19, Robert DuToit a écrit :
Hi All,
I've been off list for a while and just got around to building
rsync 3.0.6 on Mac OSX 10.6 intel core 2 duo machine. It runs
Hi All,
I've been off list for a while and just got around to building rsync
3.0.6 on Mac OSX 10.6 intel core 2 duo machine. It runs great on
similar machines but someone just said it won't for their OSX 10.6
intel core duo and returns an error:
rsync Bad CPU type in executable.
I che
Hello Carlos
Thank you for your answer.
no the exit code is 24...
I also sometimes get exit code 23, but then rsync does it correctly...
What would be the effect of the file system reporting "permission
denied" while reading directories? A list with files missing ?
HC
Carlos Carvalho skre