Displaying 1 result from an estimated 1 matches for "on_nonblock".
Did you mean:
o_nonblock
2004 Nov 17
1
specifying --bwlimit together with --daemon fails
I received a bug report that starting with 2.6.3, rsync fails when
started from inetd with the --bwlimit option (actually, I narrowed it
down to that :-). Earlier rsync versions did work.
What I see from the strace output is that the rsync --daemon process
sets fd 0 to ON_NONBLOCK, then does a select() on fd 0 for write (which
shows it's ready for writing), and then does a write of zero bytes,
which returns 0 (of course), and that is apparently interpreted as a
failure, at which point it syslogs the following:
Nov 17 19:07:38 preston rsyncd[610]: rsync: writefd_unbuffer...