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.
On 11/09/2012 12:18 AM, Rüdiger Kupper wrote: config, clusterssh
> Public bug reported:
>
> Since the config file has been moved to ~/.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