On 11/09/2012 12:18 AM, RĂ¼diger Kupper wrote:
> Public bug reported:
> 
> Since the config file has been moved to ~/.clusterssh/config, clusterssh
> does not use the config option "command" any longer.
> 
> Instead, the command passed to ssh is always empty. This is revealed by
> the debug message printed in the terminal:
> 
> Running:ssh -x -o ConnectTimeout=10 -t <servername> "" ; echo Press
> RETURN to continue; read IGNORE
> 
> The command passed after <servername> is always the empty string, no
> matter what the config file specifies for "command=".

Hello RĂ¼diger,

Thank you for the bug report and pointing out this behavior.  It is a
bit strange - it appears that the upstream author pruned the support for
the command configuration option, but left the empty "" in place.

It's a simple patch to restore the functionality.  I'll look at
restoring it to the manpage as well.

Cheers,
tony

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1076897

Title:
  clusterssh does not use "command" configuration option any more

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/clusterssh/+bug/1076897/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

Reply via email to