summaryrefslogtreecommitdiffstats
path: root/subcmds/smartsync.py
diff options
context:
space:
mode:
authorShawn O. Pearce <sop@google.com>2010-05-11 18:21:33 -0700
committerShawn O. Pearce <sop@google.com>2010-05-11 18:31:47 -0700
commitca8c32cd7ae7c3ae27bb6b649eafbfd54d77f916 (patch)
tree20d74c26df2112515313b0b22c7358427bad8b57 /subcmds/smartsync.py
parentf0a9a1a30e60e92cec9bff4cae030478c276da4d (diff)
downloadgit-repo-ca8c32cd7ae7c3ae27bb6b649eafbfd54d77f916.tar.gz
sync: kill git fetch process before SSH control master processv1.6.9.6
If the SSH control master process is killed while an active git fetch is using its network socket, the underlying SSH client may not realize the connection was broken. This can lead to both the client and the server waiting indefinitely for network messages which will never be sent. Work around the problem by keeping track of any processes that use the tunnels we establish. If we are about to kill any of the SSH control masters that we started, ensure the clients using them are successfully killed first. Change-Id: Ida6c124dcb0c6a26bf7dd69cba2fbdc2ecd5b2fc Signed-off-by: Shawn O. Pearce <sop@google.com>
Diffstat (limited to 'subcmds/smartsync.py')
0 files changed, 0 insertions, 0 deletions