Bug 5071 - Enhancement Request - Customizable Connection Timeout Option
Summary: Enhancement Request - Customizable Connection Timeout Option
Alias: None
Product: rsync
Classification: Unclassified
Component: core (show other bugs)
Version: 2.6.9
Hardware: Other Other
: P3 enhancement (vote)
Target Milestone: ---
Assignee: Wayne Davison
QA Contact: Rsync QA Contact
Depends on:
Reported: 2007-11-11 00:24 UTC by Dusty Doris
Modified: 2008-02-06 21:21 UTC (History)
0 users

See Also:


Note You need to log in before you can comment on or make changes to this bug.
Description Dusty Doris 2007-11-11 00:24:19 UTC
It would be nice if we could customize connection timeouts, rather than waiting for the default timeout.  It appears someone has submitted a patch for this in the past.  I never saw any follow-ups to see if this was something that was being considered.

Comment 1 Olivier Thauvin 2007-11-11 00:47:52 UTC
Isn't timeout option what you want:

--timeout=TIME          set I/O timeout in seconds

If yes, I let you to close the bugs.
Comment 2 Dusty Doris 2007-11-11 01:00:48 UTC
I'm looking for connection timeout, rather than I/O timeout.  When I send a SYN and never get an ACK, it hangs until a default timeout.  For example, a netstat only shows SYN_SENT.

rsync: failed to connect to x.x.x: Connection timed out (110)
rsync error: error in socket IO (code 10) at clientserver.c(107) [receiver=2.6.8]
Comment 3 Wayne Davison 2007-11-11 17:01:07 UTC
Yes, I snagged that patch but apparently neglected to check it in.  There was a little tweaking I wanted to do to it before accepting it, which I worked on a bit this morning:


Since it's so simple, I'm thinking of including it in the 3.0.0 release.
Comment 4 Matt McCutchen 2008-02-06 21:21:59 UTC
The current development rsync has the --contimeout option.