Displaying 2 results from an estimated 2 matches for "31izd".
Did you mean:
31d
2016 Oct 16
1
rsync: connection unexpectedly closed
...], [3], {60, 0}) = 0 (Timeout)
(last line repeats a couple hundred times)
...and apparently the second rsync server side process is actually
still performing reads and writes more than an hour after the
connection died...
...
read(1, "\337\363\356\1^\26L\316\17\31izD\254\27\346\267\266H\343\223\v\357\252d'h\351\371\0ny"..., 262144) = 262144
write(3, "\337\363\356\1^\26L\316\17\31izD\254\27\346\267\266H\343\223\v\357\252d'h\351\371\0ny"..., 262144) = 262144
...
This makes me wonder if this has something to do with memory buffe...
2016 Oct 13
5
rsync: connection unexpectedly closed
On Wed, 2016-10-12 at 08:36 +0200, Paul Slootman wrote:
> As always it's best to first upgrade to the current version (3.1.3)
> if at all possible, as there's always the chance that the cause of
> your problems has already been fixed.
Good call, but I believe I may have ruled this out. I didn't upgrade to
3.1.3, but both sides are running 3.1.1 protocol version 31 now. Same