Date: Tue, 18 Dec 2001 16:56:42 -0500 (EST) From: "Brandon D. Valentine" <bandix@looksharp.net> To: Holt Grendal <holtor@yahoo.com> Cc: <questions@freebsd.org>, <stable@freebsd.org> Subject: Re: Hung SSH2 Logins Message-ID: <20011218165351.Q9162-100000@turtle.looksharp.net> In-Reply-To: <20011218140503.94565.qmail@web11602.mail.yahoo.com>
next in thread | previous in thread | raw e-mail | index | archive | help
[Redirected to -questions; please reply there] On Tue, 18 Dec 2001, Holt Grendal wrote: >Hi, > >After switching to support SSH2 on all of our public >access servers we began to see things like this >show up in 'w' output: > >user1 p1 hostname1 8:53AM 2 - >user2 p2 hostname2 6:50AM 1:36 - > >So far i've reached the conclusion that those users >use SecureCRT as their SSH2 client and when you press >disconnect or simply close SecureCRT it leaves a dead >login like that. > >It doesn't leave SSH running or anything like that but >it doesn't seem to close the login entry in >/var/log/wtmp (i think it is?) > >When someone goes to login in they simply re-use that >same PTY and it goes away. > >I was wondering if this is a problem in OpenSSH or the >way SecureCRT does its disconnecting? > >This problem did not occur with SSH1. > >Any ideas? What happens if you users type "exit" from the shell instead of just dropping the connection? Sounds to me like you have a user education issue coupled with the fact that SecureCRT probably doesn't disconnect cleanly on its own. Brandon D. Valentine -- "Iam mens praetrepidans avet vagari." - G. Valerius Catullus, Carmina, XLVI To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20011218165351.Q9162-100000>