On Wed, 2004-01-14 at 10:05, G. M. Bodnar wrote: > On Wed, Jan 14, 2004 at 09:53:44AM NZDT, Jim Cheetham wrote: > > I've been having my (unused interactive) ssh shells closed after a > > timeout, on some servers. Seeing as I'm often opening tunnels with > > these, that's a curse. > > Have a glance at spinner: http://www.laffeycomputer.com/spinner.html > It's a handy little tool for just this purpose.
It's an interesting hack, but besides the essential 'coolness' there are quite a few drawbacks, to do with spinner's drawn characters unpredictably ending up in the keyboard buffer, and so on. Of couse, my method has a drawback too - it's only going to work with shells that have a timeout feature that can be set by environment variable, and loses shell environment (although I could probably do something with a .logout file to save the settings) However, it's more of a "here's how to do something yourself" rather than a "install this ap" approach :-) The Right Thing to do is to find out just where the timeout is being enforced, and stop it. However, it's often a firewall, and unless you admin it yourself, you can forget about getting it changed :-) -jim
