#1
|
|||
|
|||
have to click twice to disconnect
hi, the ssh won't disconnect until I hit the disconnect icon a 2nd time, any ideas?
thanks, |
#2
|
|||
|
|||
Hello alexl,
What version of SecureCRT are you using? From your description, I think you are talking about behavior that was changed (around v6.5) to more accurately reflect the state that exists between remote and server. To revert to the prior behavior, there is an .ini only option you can change. For now, you will have to change each session's .ini file, but if you also make the change to the Default.ini file, future sessions that are created will exhibit this as the default behavior. Session .ini files (and the Default.ini) are stored in the configuration folder. The location of your installation's Configuration folder is found in the General category of SecureCRT's Global Options. To configure this:
D:"Force Close On Exit"=00000000toD:"Force Close On Exit"=00000001 I have also added this thread to a feature request in our product enhancement database to expose Force Close on Exit option in the GUI. Should a future release of SecureCRT include this feature, notification will be posted here. If you prefer direct e-mail notification, contact support@vandyke.com and include "Feature Request - Forum Thread #11067" in the subject line.
__________________
Thanks, --Brenda VanDyke Software Technical Support support@vandyke.com (505) 332-5730 |
#3
|
|||
|
|||
Any ideas on how to do (script?) this for a few 1000 .ini files on a windows system?
|
#4
|
|||
|
|||
Hello koenv,
So all your 1000+ connections require you to disconnect twice? If so, working together I think we can come up with a scripting solution, but have you made the change manually to one or two devices and verified it fixes the issue for you? What version of SecureCRT are you using?
__________________
Thanks, --Brenda VanDyke Software Technical Support support@vandyke.com (505) 332-5730 |
#5
|
|||
|
|||
Quote:
I don't always need to disconnect twice for all my devices but yes, all my devices require this when rebooting/upgrading/... Not a major issue, but annoying nonetheless. If it is a simple thing to script, please do provide the solution as I'd love to get rid of this, but on the other side, it's not worth 30mins off my time ![]() |
#6
|
|||
|
|||
Hi Koenv,
Thanks for the clarification. I have attached an example script. First, you will be prompted with a dialog where you enter the .ini option you wish to change. It is important this is entered exactly as it appears in the .ini file, so that should be: Force Close On Exit Then, if you want to change all sessions, accept the default in the second dialog. The third dialog box prompts you for the new value. In this case, you would enter 1. The log file that summarizes the actions that were taken would then be displayed. (See attached screenshots.)
__________________
Thanks, --Brenda VanDyke Software Technical Support support@vandyke.com (505) 332-5730 |
#7
|
||||
|
||||
The option to force the session channel to close on disconnect has been added to the GUI in a pre-beta version of SecureCRT. If you would be interested in trying it, please send email to me at Maureen.Jett@vandyke.com.
Maureen |
#8
|
|||
|
|||
Quote:
If so, where do I find that toggle? |
#9
|
|||
|
|||
Hi koenv,
This option is available in SecureCRT 7.2. The option is located in the Connection / SSH2 / Advanced category of the Session Options dialog, and it is named Force session channel to close on disconnect. Last edited by rtb; 07-28-2014 at 09:37 AM. |
#10
|
|||
|
|||
Quote:
![]() Running Version 7.2.2 (x64 build 491) - Official Release - March 20, 2014 and already found that trigger in the location you mentioned! |
#11
|
|||
|
|||
Hi koenv,
You are correct. My mistake. I have amended my post. |
![]() |
Currently Active Users Viewing This Thread: 1 (0 members and 1 guests) | |
Thread Tools | |
Display Modes | |
|
|