I use screen to keep terminals active for long periods of time using
the following:
hardstatus alwayslastline "%-Lw%{=3D BW}%50>%n%f* %t%{-}%+Lw%< %=3D[%D, %m/=
%d %c]"

in my .screenrc.  It will put up a clock and some other stuff that
keeps the screen updating.  I'm not sure why the non-screen terminal
is staying active.  Maybe you have a timeout set somewhere.  Here are
some other lines:
hardstatus alwayslastline "%{wk}%?%-Lw%?%{bw}%n*%f %t%?(%u)%?%{wk}%?%+Lw%=
=3D %{mk
}@ %H %{ck}%Y%{wk}-%{ck}%m%{wk}-%{ck}%d %{yk}%D %{gk}%c"
hardstatus alwayslastline "%{gk}%c %{yk}%D %{ck}%Y%{wk}-%{ck}%m%{wk}-%{ck}%=
d%=3D %
{mk}%H %{wk}%?%-Lw%?%{bw}%n*%f %t%?(%u)%?%{wk}%?%+Lw"


On 9/19/05, Christopher W. Richardson <cwr@nexthop.com> wrote:
> -----BEGIN PGP SIGNED MESSAGE-----
> Hash: SHA1
>=20
> Hey folks,
>=20
> This has been bugging me for at least a year now (maybe much
> longer, but I don't want to trust my memory that much).  It's
> been low priority, but I have a few minutes, so I thought I'd
> ask.
>=20
> It is very common practice for me to have to ssh sessions up
> between my laptop at home and my work workstation.  Typically,
> one of these is just a terminal, and the other is a terminal
> running screen.  Inevitably, if I leave it over night, the one in
> which screen is running has disconnected (and the other one
> hasn't).  Like I said, it's not a huge deal at all, since screen
> is running; more of just a curiosity.  What gives?  Any ideas?
>=20
> The machine at home is running Windows and using putty as the ssh
> client.  The one at work has been running various versions of
> NetBSD i386 from 1.6 to 2.0.2_STABLE.
>=20
> Thanks,
> Chris
> -----BEGIN PGP SIGNATURE-----
> Version: GnuPG v1.4.2 (NetBSD)
> Comment: Processed by Mailcrypt 3.5.8 <http://mailcrypt.sourceforge.net/>
>=20
> iD8DBQFDL0Z4P65RBOOHTzERAtvXAKDPSyGWolMqWrldJXsNSGNObKe0qQCgynYU
> IOWbsTbcXJdIkx1kMw08TGE=3D
> =3DScFL
> -----END PGP SIGNATURE-----
>