diff options
| author | Daniel Kahn Gillmor <dkg@fifthhorseman.net> | 2008-09-14 17:48:56 -0400 |
|---|---|---|
| committer | Daniel Kahn Gillmor <dkg@fifthhorseman.net> | 2008-09-14 17:48:56 -0400 |
| commit | 9f65b455d187cfc86767de355a540f4ea19560b5 (patch) | |
| tree | 7edbb2fb83bc82e6b9ea2e595a057b1c10e48455 /website/bugs/cssh-connection-timeout.mdwn | |
| parent | 12664ba44bd38efbfd9e6571b937035a5695cdaa (diff) | |
| parent | cc637b08d6404c3d90926713da8286cae0ebd279 (diff) | |
Merge commit 'jamie/master'
Diffstat (limited to 'website/bugs/cssh-connection-timeout.mdwn')
| -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 |