Content-Type: TEXT/PLAIN; CHARSET=US-ASCII
On 4 Feb 2003, Tony Gale wrote:
> On Mon, 2003-02-03 at 21:04, Bill Davidsen wrote:
> > That is a problem with processes left running. I do not forward
> > connections, I do not forward X, I do not (in normal practice) leave
> > anything running. A typical thing to do is to go to each machine in a
> > cluster and look for a user activity:
> > grep "user" log/stats.readers
> > exit
> > nothing more. And every once in a while that hangs after executing the
> > logout sequence. With the patch it hasn't to date.
> > That doesn't mean it's a fix, I don't see it every day, I just haven't
> > seen it in a few days since I put in the patch.
> The ssh hang on exit "problem" is a policy of the ssh coders. It'll
> happen when you have a background job still running when you exit, which
> is still connected to the terminal.
Please go back and reread either of my comments on the topic, I think I've
made it clear that I have no background jobs, no forwarded ports, and no
forwarded X. The existance of a problem in one area doesn't mean that
nothing else is allow to cause bad behaviour.
> As I said, it's an ssh policy issue (which many people disagree with)
> and not a bug.
-- bill davidsen <firstname.lastname@example.org> CTO, TMR Associates, Inc Doing interesting things with little computers since 1979.
--=_courier-30851-1044370032-0001-2 Content-Type: application/pgp-signature; name="signature.asc" Content-Transfer-Encoding: 7bit Content-ID: <Pine.LNX.3.96.1030204093748.32005D@gatekeeper.tmr.com> Content-Description: This is a digitally signed message part
-----BEGIN PGP SIGNATURE----- Version: GnuPG v1.2.0 (GNU/Linux)
iQCVAwUAPj+O0h/0GZs/Z0FlAQKbkgQAzRglvGGrNxRdod0gWhs93eYFG3KwkJ/a LkJ9HoxAhItOcLXQOyuarJHooq44ME9Ym3Q3N2FpjFVsbrVi+/DIh2hQlF9QW/f5 PyjZIYQRBsebLm/U9uI9wqPfqaNM6jC8ulU1cRQfrYJ9CkIKhBhtbG1a7VuATgCi S4eP/vovOx8= =5H++ -----END PGP SIGNATURE-----