X-Git-Url: https://codewiz.org/gitweb?a=blobdiff_plain;f=website%2Fbugs%2Fcssh-connection-timeout.mdwn;h=046ca12d6b5420c7665cb5f89ac844f29cc8a3bb;hb=792f1e3324076f8521de33aa15f1dd7ba9c9a73f;hp=073b0cf879adce80e105fb32a055e51f0424ef7f;hpb=0c63107a90d9fcb43f78fdd47c041c35ac4599df;p=monkeysphere.git

diff --git a/website/bugs/cssh-connection-timeout.mdwn b/website/bugs/cssh-connection-timeout.mdwn
index 073b0cf..046ca12 100644
--- a/website/bugs/cssh-connection-timeout.mdwn
+++ b/website/bugs/cssh-connection-timeout.mdwn
@@ -71,3 +71,23 @@ 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
+
+I just [posted the cssh bug in debian](http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=498968).