From: Jamie McClelland <jm@mayfirst.org>
Date: Sun, 14 Sep 2008 20:20:51 +0000 (-0400)
Subject: closing cssh bug.
X-Git-Tag: monkeysphere_0.16-1~39^2~3
X-Git-Url: http://git.tremily.us/?a=commitdiff_plain;h=cc637b08d6404c3d90926713da8286cae0ebd279;p=monkeysphere.git

closing cssh bug.
---

diff --git a/website/bugs/cssh-connection-timeout.mdwn b/website/bugs/cssh-connection-timeout.mdwn
index 073b0cf..8a70bb7 100644
--- a/website/bugs/cssh-connection-timeout.mdwn
+++ b/website/bugs/cssh-connection-timeout.mdwn
@@ -71,3 +71,21 @@ that a longer connection timeout is acceptable:
 Perhaps this is an acceptable workaround?
 
 -- dkg
+
+---
+
+Sorry for not being more clear. Monkeysphere debug does not reveal personal
+information - but cluster cssh -d -D exposes the hosts in my ssh config file.
+
+dkg's approach seems to work. His suggestion, as written, didn't work for me.
+But that's because I ran cssh -u > $HOME/.csshrc, which generates a default
+cssh config file (that specifies ConnectTimeout=10). That file seems to
+override the command linke (perhaps a cssh bug?). I changed the ConnectTimeout
+to 30 in my ~/.csshrc file and now everything works. 
+
+I think jrollins' assessment is probably right - the extra delay due to locking
+causes the timeout. I think tweaking ConnectTimeout parameter via the .csshrc
+file or via the command line is a reasonable fix for this bug, so I'm closing
+as [[bugs/done]].
+
+-- Sir Jam Jam