The admin guide p 127 says:
To specify the maximum idle time for a connection with a Network Shell client,
enter the following:
set appserver IdleNshProxyPruneTime #
where # is a value in minutes. When there is no traffic over the connection between
a Network Shell client and its proxy for this period of time, the connection is
automatically closed. By default this value is set to 0, which means the connection
is never closed.
So I think that's the setting you want. What did you set that do, and did you restart the appserver after you made the settings changes?
Yup thats the one i went for and set it to 1 as a tester. So this should mean 1 min right?
1) Can confirm my secure file is pointing to the test BLAPP server
2) confirm IdleNshProxyPruneTime:1 is set on Test BLAPP and restarted
3) Opened up nsh from my desktop, log in, and cd //<test server>
4) checked connection via infrastructure management, confirmed connection on NshProxyConnectionService:
So its been more than 2 mins, but connection is still active?
as soon as i action something like, "ls", on my nsh shell, the connection Idle time resets to:
What should i expect to see anyways when it force closes the idle nsh connection? The NshProxyConnectionService automatically cutting that connection off when it hits 1min and when i attempt to use the nsh shell it'll prompt me that session has ended/disconnected/timed out?
Thanks in advance guys,
And you've got the client configured to go through the nsh proxy? (in the secure file)?
Yup, secure file entry:
and on test BLAPP box:
...I'm missing something here arent i?
You should be using the sso proxy, the proxy you are using is the 'legacy' proxy.
What version of bladelogic are you using?
126.96.36.199 (testing it out at the moment)
and bummer...*flicks through that admin guide again*
auth_profiles_file=/c/Program Files/BMC BladeLogic/OM/br