Seperate logfile per cloned session

[jclark1978]

At work we use a linux jumpbox to access multiple hosts. To login to the jumpbox we need to use an RSA passcode but once we SSH to a host from there it's a static password to allow for faster connectivity.

I have a script which allows me to
1. Clone the jumpbox session,
2. Prompts for a host name
3. SSH to a host,
4. Rename the tab with the hostname

It's working great and is a huge time saver.

As my job demands accessing multiple hosts simultaneously I'm typically logged into multiple hosts in multiple tabs simultaneously and would like to have a separate log file per cloned session with the name of the variable %hostname% (shown in step 2 above).

I've been able to change the log file name using "crt.Session.LogFileName = logfile" with the variable %hostname% as I've seen in other posts but this only seems to work the first time I run it. Anyone else have any experience with generating unique logfiles in cloned sessions?

Thanks,

~ Jeff

[bgagnon]

Hi Jeff,

Renaming the tab in the way described is only a temporary change. See attached.

I have a script which allows me to
1. Clone the jumpbox session,

How are you cloning the jumpbox session?

What I think might help in your scenario is to have a unique session name in order to generate unique log files and that can be accomplished a couple of ways.

If using v7.1.x or later, are you aware of this functionality that was added?

Changes in SecureCRT 7.1 (Beta 1) -- February 26, 2013
------------------------------------------------------

New features:

• Added support for dependent sessions so that a connection can be made to a jump host or SSH gateway before the session is connected.

I've been able to change the log file name using "crt.Session.LogFileName = logfile" with the variable %hostname% as I've seen in other posts but this only seems to work the first time I run it. Anyone else have any experience with generating unique logfiles in cloned sessions?

We would need more details about your script to assist with solving this issue. It would be best to contact us directly via email at support@vandyke.com and reference "Forum Thread #12258" in the subject line.