1) Remote login by sshing into a server -- the server logs you out after 1 hour or a bit less 2) If sshing on the same network, it will not log you out. This look like good to use some sort of script in the login scripts. On 8/18/05, Jonathan Chen (jonachen) <jonachen@xxxxxxxxx> wrote: > > TMOUT is a good idea. But the problem is RHEL 3 is already doing it > and I would like to turn the feature off or change the timeout. > > Regarding the SSHD_CONFIG file...it does not work when I played around > with the settings. The server already have KEEPALIVE ON. So where > is that feature at? > > Repeating problem: > > 1) Remote login by sshing into a server -- the server logs you out > after 1 hour or a bit less > 2) If sshing on the same network, it will not log you out. > > > So where is the feature that logs me off all the time when using a > Windows SSH client? > > ========================================== > From: ubergoonz <ubergoonz gmail com> > To: me gavitron com, General Red Hat Linux discussion list <redhat-list > redhat com> > Cc: > Subject: Re: Automatic disconnect from host feature > Date: Wed, 17 Aug 2005 10:36:33 +0800 > > ------------------------------------------------------------------------ > -------- > > use TMOUT shell variable ? > > On 8/17/05, Gavin McDonald <gavitron gmail com> wrote: > > > > >-----Original Message----- > > >From: redhat-list-bounces redhat com > > [mailto:redhat-list->bounces redhat com] On Behalf Of Jonathan Chen > > (jonachen) > > >Sent: Monday, August 15, 2005 3:40 PM > > >To: redhat-list redhat com > > >Subject: RE: Automatic disconnect from host feature > > > > > >> > > >> Two (or three) thoughts: > > >> > > >> 1) It depends on how they are connecting. If you are talking > > >> about local > > >> sessions, that is far different than say, remote X > > >> connections, or even > > >> remote connections over VNC, or X tunneled through SSH. > > > > > >Well I'm talking about using using a regular windows SSH client to > > >connect to linux host and also later with X session using FreeNX. > > Later, as in "After the ssh is connected"? Because if you are using > > X-forwarding through ssh, then it is still dependant on the ssh > connection > > terminating unexpectedly. > > > > > > >> 2) It will probably be service-based timeouts, for example SSH has > > >> keepalive=YES and probably a timeout option as well (man ssh) > > > > > >I don't believe this works at all. Where is the setting that says to > > >let users be on the system until they log out when they are on the > same > > >network while from another network, you will be logged off after an > > >hour??? > > > > try > > # man sshd_config > > and > > # man ssh_config > > > > and look at the following settings > > TCPKeepAlive > > ServerAliveInterval > > ServerAliveCountMax > > > > I do not claim to be an expert, but I have never even heard of a > setting > > that specifically sets timeouts for remote users only. If you have > seen > > a system like this in operation, Go ask the sysadmin how he built it? > > > > That said, perhaps you are looking more for something like Process > > accounting? > > > > Regards, > > Gavin. > > > > -- > redhat-list mailing list > unsubscribe mailto:redhat-list-request@xxxxxxxxxx?subject=unsubscribe > https://www.redhat.com/mailman/listinfo/redhat-list > -- Best Regards, Leslie Joshua Wang +============================================================+ "I believe there's a hero in everyone of us, give us strength, make us noble, even though sometimes, we have to give up the things we want the most." +============================================================+ "The good thing about standard, there are so many of them to chose from ..." availability, performance and cost - pick 2 -- redhat-list mailing list unsubscribe mailto:redhat-list-request@xxxxxxxxxx?subjecthttps://www.redhat.com/mailman/listinfo/redhat-list
