clone and pull "premature EOF"
Cameron Simpson
cs at zip.com.au
Mon May 10 02:41:21 UTC 2010
On 07May2010 15:35, Paul Copeland <tech at jotobjects.com> wrote:
| We have had 5 clients failing some intermittently and some consistently.
[ ... both linux and windows ... ]
| The server people are looking into it... [...]
Speaking as a network/firewall/OS guy rather than a mercurial guy,
is it possible that a stateful firewall has decided the connection is
idle? Matt, are there periods where the hg pull might send no data in
either direction for an extended period?
Anyway, to circumvent the idleness try using:
ssh -o ServerAliveInterval=10
or put:
ServerAliveInterval 10
in your .ssh/config file at the client end. That ought to periodicly
send a ping in the ssh protocol, keeping the connection "awake" from the
point of view of a firewall, without affecting the hg data protocol.
From "man ssh_config":
ServerAliveInterval
Sets a timeout interval in seconds after which if no data has been
received from the server, ssh(1) will send a message through the
encrypted channel to request a response from the server. The default is
0, indicating that these messages will not be sent to the server. This
option applies to protocol version 2 only.
It may be interesting to see if this changes the behaviour.
If it reliably makes stuff work, i would suspect a firewall getting
bored.
Cheers,
--
Cameron Simpson <cs at zip.com.au> DoD#743
http://www.cskk.ezoshosting.com/cs/
[Alain] had been looking at his dashboard, and had not seen me, so I
ran into him. - Jean Alesi on his qualifying prang at Imola '93
More information about the Mercurial
mailing list