Auto Login parameters

Gary - Tue 08/05/2012 16:56:19 CEST +0200

We have many servers that we connect to. Many of these we cannot connect to directly, so we have to SSH onto one server and from there SSH to the other servers.

As a result, we have many similar post-login scripts, typically with just an IP address or server name different.

I'd love to be able to put that IP address or server name as a parameter to the Login script file.

I have tried setting an Environment Variable (and thus using ssh user@$variable), but our servers won't allow them to be set. Hence the request.

Gary - Wed 13/06/2012 17:19:38 CEST +0200

Any answer for this? A yes/no, will do/won't do, even?

- Thu 14/06/2012 07:51:39 CEST +0200

You must create several sessions that differ with the auto-command.

Gary - Thu 21/06/2012 12:37:59 CEST +0200

Can something like this be added to a future version of Kitty?
Within the next couple of weeks we will be running in an environment that has about 200+ servers. At the moment, this means 200+ scripts, all of which are the same apart from maybe 1 line. So some sort of parametrisation would mean we could cut this down to a handful of scripts and add the parameters into Kitty.

Cyd - Fri 22/06/2012 07:48:10 CEST +0200

Why don't you use -cmd parameter ?

Gary - Wed 27/06/2012 15:34:20 CEST +0200

Hi Cyd,

-cmd: to define a startup auto-command

This isn't very descriptive. How can I use this to do what I want? What is the startup command and where is it located?

As you suggesting, maybe, that I could use this to run a script on server? If so, this still leave issues with running 'sudo' commands on those servers as the password will be requested, and the password changes every 2 months. This would mean editing around 300 scripts across all of the servers to update the password.

If the script is held locally, then it would still need parameters as there would be IP addresses that would be different for different connections.

For many servers, we do not have direct access to it. We have to login to server A, and from there from ssh to the server we want to connect to, so we need to change the IP address. Then we need to run a sudo command to change user (as we cannot login direct as the final user).

In short, complicated. I'm looking for a way to make this easier.

Answer

Currently the forum is closed