https://bugzilla.samba.org/show_bug.cgi?id=15163
--- Comment #6 from roland ---
nobody has a clue?
i think proper rsync timeout handling is important.
i have had whole nightly backup procedures hung for the whole night because
rsync got stuck and didn't get timeout, i.e. machines did not get
https://bugzilla.samba.org/show_bug.cgi?id=15163
--- Comment #5 from roland ---
apparently, this is causing the problem:
if (am_receiver) {
return;
}
if i comment out the return statement, things work again.
@wayne, what is the reason that timeout checking
https://bugzilla.samba.org/show_bug.cgi?id=15163
--- Comment #4 from roland ---
here with debug=all
working correctly
# /root/rsync/rsync-3.2.5/rsync -avi --timeout=5 --exclude='/proc'
--exclude='/dev/' --exclude='/sys' --debug=all --msgs2stderr
root@172.20.37.189:/iscsipool
https://bugzilla.samba.org/show_bug.cgi?id=15163
--- Comment #3 from roland ---
ah, getting a clue
in io.c
static void check_timeout(BOOL allow_keepalive, int keepalive_flags)
{
time_t t, chk;
/* On the receiving side, the generator is now the one that decides
* when
https://bugzilla.samba.org/show_bug.cgi?id=15163
--- Comment #2 from roland ---
here is another bugreport, where timeout is not effective/working
https://bugzilla.redhat.com/show_bug.cgi?id=1944132
--
You are receiving this mail because:
You are the QA Contact for the bug.
--
Please use
