add some rough instructions on getting the extension/perl validation agent going...

[monkeysphere.git] / website / bugs / cssh-connection-timeout.mdwn

diff --git a/website/bugs/cssh-connection-timeout.mdwn b/website/bugs/cssh-connection-timeout.mdwn
index 073b0cf879adce80e105fb32a055e51f0424ef7f..343d5af0977e4b95451102b73103f5b0b77c61c5 100644 (file)
--- a/website/bugs/cssh-connection-timeout.mdwn
+++ b/website/bugs/cssh-connection-timeout.mdwn
@@ -1,4 +1,4 @@
-[[meta title="Monkeysphere interferes with clusterssh"]]
+[[!meta title="Monkeysphere interferes with clusterssh"]]
 
 clusterssh is a package that allows you to control multiple ssh xterm
 sessions at the same time.
@@ -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).