Package: clusterssh
Version: 3.19.1-3
Severity: important
cssh gets confused by directories in . that are named like the binaries
it wants to execute.
The problem is in line 232, where to check if we already are configured
we test if "$binary" is executeable:
| if ( ! -x $binary )
by default this gets called with 'ssh' and '/usr/bin/xterm'.
[EMAIL PROTECTED]:~$ mkdir ssh
[EMAIL PROTECTED]:~$ cssh asteria
Terminal binary not found (ssh) - please amend $PATH or the cssh config file
Died at /usr/bin/cssh line 263.
I think the find_binary() function should be slightly changed:
- if $binary has a / in its name somewhere, test if it's an executable
file. if yes, be happy, if no bail out.
- otherwise, do the PATH searching dance:
--- /usr/bin/cssh 2006-11-05 20:29:52.000000000 +0100
+++ cssh 2006-11-05 20:30:52.471959807 +0100
@@ -229,7 +229,7 @@
logmsg( 2, "Looking for $binary" );
my $path;
- if ( ! -x $binary )
+ unless ( $binary =~ m#/# )
{
# search the users $PATH and then a few other places to find the binary
# just in case $PATH isnt set up right
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
