diff options
author | Jamie McClelland <jm@mayfirst.org> | 2008-09-14 16:20:51 -0400 |
---|---|---|
committer | Jamie McClelland <jm@mayfirst.org> | 2008-09-14 16:20:51 -0400 |
commit | cc637b08d6404c3d90926713da8286cae0ebd279 (patch) | |
tree | 796f126717e91b44bc11c7fad635cfd21d621a52 /website | |
parent | 2b85b853a3173ba5157e094dac0be5c21c062d51 (diff) |
closing cssh bug.
Diffstat (limited to 'website')
-rw-r--r-- | website/bugs/cssh-connection-timeout.mdwn | 18 |
1 files changed, 18 insertions, 0 deletions
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 |