Displaying 2 results from an estimated 2 matches for "msg11850".
Did you mean:
msg11654
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
2005 Jan 13
1
--bwlimit doesn't work for daemon mode
[I'm not subscribed, please CC me on replies]
Some time after 2.6.0 the --bwlimit code was enhanced, but the code now
doesn't work anymore when you set the bandwidth limit for the daemon and
generates error log entries like:
2005/01/13 08:17:03 [29636] rsync: writefd_unbuffered failed to write 12 \
bytes: phase "unknown" [receiver]: Success (0)
2005/01/13 08:17:03 [29636]