clusterssh does not use "command" configuration option any more

[Rüdiger Kupper]

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=".

ProblemType: Bug
DistroRelease: Ubuntu 12.10
Package: clusterssh 4.01.01-4
ProcVersionSignature: Ubuntu 3.5.0-18.29-generic 3.5.7
Uname: Linux 3.5.0-18-generic i686
ApportVersion: 2.6.1-0ubuntu6
Architecture: i386
Date: Fri Nov 9 09:08:22 2012
MarkForUpload: True
PackageArchitecture: all
SourcePackage: clusterssh
UpgradeStatus: Upgraded to quantal on 2012-10-21 (19 days ago)

[Rüdiger Kupper (ruediger.kupper)]

Addition: the config option "command" is not even documented in the manpage any longer. Has it been forgotten?

[Tony Mancill (tmancill)]

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

[Rüdiger Kupper (ruediger.kupper)]

Hello Tony,

thank you for looking into it. Clusterssh is a great tool for admins. I use it daily for administering our school servers. I use(d) the "command=" option to have clusterssh connect to "screen" sessions automatically.

[Tony Mancill (tmancill)]

On 11/11/2012 03:05 AM, Rüdiger Kupper wrote:

> thank you for looking into it. Clusterssh is a great tool for admins. I
> use it daily for administering our school servers. I use(d) the
> "command=" option to have clusterssh connect to "screen" sessions
> automatically.

Yes, Duncan Ferguson has done a nice job with clusterssh. It looks like
the support for "command" has been pulled out of the configuration file
handling, so it's going to take me a bit longer than I thought.

In the meantime, can you achieve the same functionality with the
--action/-a switch on the command-line? I realize that it might still
be useful to support this via the configuration file.

Cheers,
tony

[Rüdiger Kupper (ruediger.kupper)]

Yes, the "action" switch achieves the same functionality. The best way
to support this in the config file would probably be a configuration
option called "action=". During upgrade, the "command=" entry in an
existing config file should be changed to "action=".

On Mon, Nov 12, 2012 at 4:13 AM, Tony Mancill <email address hidden> wrote:
> On 11/11/2012 03:05 AM, Rüdiger Kupper wrote:
>
>> thank you for looking into it. Clusterssh is a great tool for admins. I
>> use it daily for administering our school servers. I use(d) the
>> "command=" option to have clusterssh connect to "screen" sessions
>> automatically.
>
> Yes, Duncan Ferguson has done a nice job with clusterssh. It looks like
> the support for "command" has been pulled out of the configuration file
> handling, so it's going to take me a bit longer than I thought.
>
> In the meantime, can you achieve the same functionality with the
> --action/-a switch on the command-line? I realize that it might still
> be useful to support this via the configuration file.
>
> Cheers,
> tony
>
> --
> You received this bug notification because you are subscribed to the bug
> report.
> https://bugs.launchpad.net/bugs/1076897
>
> Title:
> clusterssh does not use "command" configuration option any more
>
> Status in “clusterssh” package in Ubuntu:
> In Progress
>
> Bug description:
> 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=".
>
> ProblemType: Bug
> DistroRelease: Ubuntu 12.10
> Package: clusterssh 4.01.01-4
> ProcVersionSignature: Ubuntu 3.5.0-18.29-generic 3.5.7
> Uname: Linux 3.5.0-18-generic i686
> ApportVersion: 2.6.1-0ubuntu6
> Architecture: i386
> Date: Fri Nov 9 09:08:22 2012
> MarkForUpload: True
> PackageArchitecture: all
> SourcePackage: clusterssh
> UpgradeStatus: Upgraded to quantal on 2012-10-21 (19 days ago)
>
> To manage notifications about this bug go to:
> https://bugs.launchpad.net/ubuntu/+source/clusterssh/+bug/1076897/+subscriptions

--
Dr. Rüdiger Kupper
Forststr. 3
72250 Freudenstadt
Tel. 07441 / 4010532