Inactive session timer

Hi folks,

I have a wxPython app that users will open over a SSH X-Window session.
So, typically they would open an SSH session and run “python appMainFrameName.py” which will bring up the App Main Frame.

Now there are ways to look at SSH inactive session timers in Linux and disconnect them, but when you open an X session, those SSH idle timers do not apply (unless you can help me in the right direction).

Is there a way I can catch idle/inactive sessions and handle it in my own way by sending some warning that the app has been idle and will be closed?

Thanks

kma_jg wrote:

I have a wxPython app that users will open over a SSH X-Window session.
So, typically they would open an SSH session and run "python
appMainFrameName.py" which will bring up the App Main Frame.

Now there are ways to look at SSH inactive session timers in Linux and
disconnect them, but when you open an X session, those SSH idle timers
do not apply (unless you can help me in the right direction).

Well, there are no inactivity timers in SSH. The inactive session
timeouts you see are caused by TCP timers, usually implemented by a
router or gateway. SSH clients often have the ability to send "keep
alive" messages periodically to reset the TCP timeouts, but those should
work whether you are using port redirection or not.

Is there a way I can catch idle/inactive sessions and handle it in my
own way by sending some warning that the app has been idle and will be
closed?

You can set your own timer and watch for activity, but there's really no
way for you to know what the timeout is for the current connection.
Routers allow you to change that number.

···

--
Tim Roberts, timr@probo.com
Providenza & Boekelheide, Inc.