--===============2131149603==
Content-Type: multipart/alternative;
boundary="----=_Part_13834_10849379.1209695892499"

------=_Part_13834_10849379.1209695892499
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
Content-Disposition: inline

Thanks Wayne.

I'm pretty sure i grabbed the one from the build dir. Is there any way i
can tell?



On Thu, May 1, 2008 at 12:17 AM, Wayne Davison wrote:

> On Tue, Apr 29, 2008 at 10:05:07AM +1000, Ramkumar Santoshi wrote:
> > On Mac OS10.4, using rsync 3.0, it stops during a transfer.

>
> That's an incomplete version. The last release was 3.0.2.
>
> > 2008/04/28 20:48:46 [3149] rsync: writefd_unbuffered failed to write 4

> bytes [sender]: Broken pipe (32)
>
> That just tells you that the receiver went away. Run a version of rsync
> that does not have the debug symbols stripped out (i.e. use the binary
> in the build dir, not the one that is installed), enable core dumps (use
> "ulimit -c unlimited"), and use a debugger on the core dump to get a
> backtrace ("gdb /build/dir/rsync core" followed by "bt"). Then, please
> let me know where it crashed.
>
> > Also, what's the characters mean in the logfile, such as:
> > >f..tpog.... RAID_One/data/file

> > 8.39M 100% 4.12MB/s 0:00:01 (xfer#3478, to-check=1224/8633)

>
> See the --itemize-changes option and the --progress option.
>
> ..wayne..
>


------=_Part_13834_10849379.1209695892499
Content-Type: text/html; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
Content-Disposition: inline

Thanks Wayne.

 

I'm pretty sure i grabbed the one from the build dir.  Is there any way i can tell?

 


 

On Thu, May 1, 2008 at 12:17 AM, Wayne Davison <wayned@samba.org> wrote:


On Tue, Apr 29, 2008 at 10:05:07AM +1000, Ramkumar Santoshi wrote:
> On Mac OS10.4, using rsync 3.0, it stops during a transfer.

That's an incomplete version.  The last release was 3.0.2.



> 2008/04/28 20:48:46 [3149] rsync: writefd_unbuffered failed to write 4 bytes [sender]: Broken pipe (32)

That just tells you that the receiver went away.  Run a version of rsync

that does not have the debug symbols stripped out (i.e. use the binary
in the build dir, not the one that is installed), enable core dumps (use
"ulimit -c unlimited"), and use a debugger on the core dump to get a

backtrace ("gdb /build/dir/rsync core" followed by "bt").  Then, please
let me know where it crashed.


> Also, what's the characters mean in the logfile, such as:
> >f..tpog.... RAID_One/data/file
>        8.39M 100%    4.12MB/s    0:00:01 (xfer#3478, to-check=1224/8633)


See the --itemize-changes option and the --progress option.

..wayne..



------=_Part_13834_10849379.1209695892499--

--===============2131149603==
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
Content-Disposition: inline

--
Please use reply-all for most replies to avoid omitting the mailing list.
To unsubscribe or change options: https://lists.samba.org/mailman/listinfo/rsync
Before posting, read: http://www.catb.org/~esr/faqs/smart-questions.html
--===============2131149603==--