begin quoting Carl Lowenstein as of Thu, May 18, 2006 at 06:52:12PM -0700: > On 5/18/06, Stewart Stremler <[EMAIL PROTECTED]> wrote: [snip] > >Run "top" when you're not doing anything. See if anything changes. > > On the remote machine so there is always something happening?
Yup. So there's always being pushed down the wire. I've had some systems where that worked, some where it didn't. > The usual situation is that I am running trn on the remote machine, > reading net.news. Then I switch to a different desktop locally to do > something else, such as a Google search stimulated by the news > reading. If I wait too long, when I switch back to the first desktop > I am logged out. That can be annoying. Screen can help, if you are trying to avoid losing your place. > For what it's worth, a small experiment just now shows the value of > the timeout to be 10 minutes. Caused by having to go help fixing > dinner just after I logged in. "last" shows that I remained logged in > for (00:10) hours:minutes. Wonder if it's something being enforced by the OS? -- _ |\_ \| -- [email protected] http://www.kernel-panic.org/cgi-bin/mailman/listinfo/kplug-list
