BLU Discuss list archive
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
gnome termnal question
- Subject: gnome termnal question
- From: tbs-Gb/NUjX2UK8 at public.gmane.org (theBlueSage)
- Date: Fri, 12 Mar 2010 16:50:41 -0500
- In-reply-to: <4B9AA42E.9030500-prQxUZoa2zOsTnJN9+BGXg@public.gmane.org>
- References: <1268423379.6815.7.camel@corelux> <4B9AA42E.9030500@darose.net>
On Fri, 2010-03-12 at 15:29 -0500, David Rosenstrauch wrote: > On 03/12/2010 02:49 PM, theBlueSage wrote: > > Hi folks, > > > > so I do a lot of work in a lot of terminals across some 25 servers. I do > > 99% of this work in gnome terminal as I like the tabbing and all the > > bells and whistles. However it has a 'missing feature' that my coworker > > has on his windows system (secureCRT). Sometimes I am idle on a server > > for a period of time that is longer than the default timeout set by the > > server's sshd_config. Obviously I get logged out. This is a pain when I > > am tailing '-f' a file that has no output for periods of time. The > > secureCRT has a feature where it pings the connection if there is no > > human or server real activity, thus keeping the connection open and > > alive. Is there any way of setting gnome terminal to do the same thing? > > > > I know I could just lengthen or remove the default timeout on the > > server, but I am not the only person going on it, and I dont want to > > open up the possibility of everyone else leaving SSH terms open all over > > the place, sucking resources etc .... > > > > Any thoughts suggestions welcome :) > > > > Richard > > Why don't you just use Gnu screen > (http://en.wikipedia.org/wiki/Gnu_screen) and avoid the problem > altogether? Screen lets you open one or more bash sessions in a > remote/ssh connection, then leave it running and detach from it, come > back and re-attach later (from a different machine no less!) Absolutely > essential tool for any *nix admin or developer to add to their toolbox > these days! > > That said, the direct answer to the question you asked is that the SSH > client provides the "anti-timeout" function you were asking about, > though it's disabled by default. Just add "ServerAliveInterval 240" (or > some suitable length of time) to your ~/.ssh/config file. brilliant! exactly what I was looking for :) thank you! having said that I wil also checkout Gnu_screen > > HTH, > > DR > _______________________________________________ > Discuss mailing list > Discuss-mNDKBlG2WHs at public.gmane.org > http://lists.blu.org/mailman/listinfo/discuss
- References:
- gnome termnal question
- From: tbs-Gb/NUjX2UK8 at public.gmane.org (theBlueSage)
- gnome termnal question
- From: darose-prQxUZoa2zOsTnJN9+BGXg at public.gmane.org (David Rosenstrauch)
- gnome termnal question
- Prev by Date: gnome termnal question
- Next by Date: file system check software
- Previous by thread: gnome termnal question
- Next by thread: pvcreate to raid1 fails
- Index(es):