keep login session connected

keep login session connected

Post by * Tong » Sat, 21 Dec 2002 06:55:02



Hi,

One server I use (or my gateway?) kicks me out of my ssh login
session only in about 3 minutes. This is much too short.

I once saw a tools that will help me get connected. But I can't find
it any more (looked both on freshmeat or sourceforge).

Please help. Thanks

--
Tong (remove underscore(s) to reply)
  *niX Power Tools Project: http://xpt.sourceforge.net/
  - All free contribution & collection

 
 
 

keep login session connected

Post by Michael Heimin » Sat, 21 Dec 2002 09:25:04



> Hi,

> One server I use (or my gateway?) kicks me out of my ssh login
> session only in about 3 minutes. This is much too short.

> I once saw a tools that will help me get connected. But I can't find
> it any more (looked both on freshmeat or sourceforge).

You tried 'unset TMOUT'?
'man bash' for more info about it.

If this doesn't help, try setting ClientAliveInterval for the sshd,
restart it and retry. 'man sshd_config' for more info.

Good luck

Michael Heiming
Btw.
The primary group for ssh related questions:
comp.security.ssh
--
Remove +SIGNS and www. if you expect an answer, sorry for inconvenience,
but I get tons of SPAM  

 
 
 

keep login session connected

Post by Bill Marcu » Sat, 21 Dec 2002 09:35:17


On Thu, 19 Dec 2002 21:55:02 GMT,

Quote:> Hi,

> One server I use (or my gateway?) kicks me out of my ssh login
> session only in about 3 minutes. This is much too short.

> I once saw a tools that will help me get connected. But I can't find
> it any more (looked both on freshmeat or sourceforge).

screen might help you resume a session after you are disconnected.
You might need to contact the administrator of the server that kicks
you out after 3 minutes.
 
 
 

1. login sessions keep on using CPU power after being logged out.

Hello,

it seems that since 1.3.35 or 36 login keeps active after I've closed my
terminal application (I don't always correctly log out). Currently there are
two login sessions active which don't connect to a terminal program (netstat)
for more that 12 hours. They're using up to 45% CPU power each :(
If I remember this behaviour started with 1.3.35 or 36 and it hasn't
disappeared with kernels up to 41.

Can anybody reproduce this strange behaviour?
I'm using slack 2.30.

TIA,

Wanne de Kler.

PS Has the kernel mailing list disappeared ? I used to receive a digest but I
haven't seen it for over three weeks now (I've lost the email address).

2. Mounting with NFS

3. kppp: connect before login & keep connection

4. Implementing DHCP client with INIT-REBOOT state as per RFC, 'requested ip address' in dot notation?

5. Login Session Manager - adding session

6. IWILL 2930C SCSI Card?

7. 1 * kaBayoadH-pppd keeps connecting when another modem connects

8. /machine/directory displayed

9. pppd keeps connecting when another modem connects

10. Login keeps reporting "Looking at a login line"

11. Keep getting Stopped (signal) when trying to run matlab 5 over lbx X windows session

12. keep dynamic ip same throughout one dsl connection session?

13. how to audit/test if firewall keep track of state/session