unknown message 0:0 [sender]

[thomas veymont]

yes : disabling the timeout on the server side worked around the problem.
anyway, ready to test additional patches if helpful.

best-
Tom


2013/10/4 Wayne Davison <wayned at samba.org>

> On Fri, Oct 4, 2013 at 12:26 AM, thomas veymont <thomas.veymont at gmail.com>wrote:
>
>> patched the 3.1.0 io.c source ,  now I get this message on the client
>> side:
>> (...)
>> unknown message 42:0 [sender]
>>
>
> Aha, then the patch is unneeded.  The sender must be in the very-early
> file-list-sending code where it doesn't accept the full list of available
> messages.  I'll look into if we can get the receiving side to avoid such
> early-in-the-transfer keep-alive sending, but in the meantime I'd suggest
> that you either use 3.1.0 on the sending side, or disable the timeout.
>
> ..wayne..
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.samba.org/pipermail/rsync/attachments/20131007/d44e8fdb/attachment.html>