From owner-freebsd-stable Tue Dec 18 6: 5: 6 2001 Delivered-To: freebsd-stable@freebsd.org Received: from web11602.mail.yahoo.com (web11602.mail.yahoo.com [216.136.172.54]) by hub.freebsd.org (Postfix) with SMTP id 0BCD037B41B for ; Tue, 18 Dec 2001 06:05:04 -0800 (PST) Message-ID: <20011218140503.94565.qmail@web11602.mail.yahoo.com> Received: from [24.189.82.162] by web11602.mail.yahoo.com via HTTP; Tue, 18 Dec 2001 06:05:03 PST Date: Tue, 18 Dec 2001 06:05:03 -0800 (PST) From: Holt Grendal Subject: Hung SSH2 Logins To: stable@freebsd.org MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG 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? TIA Holt! __________________________________________________ Do You Yahoo!? Check out Yahoo! Shopping and Yahoo! Auctions for all of your unique holiday gifts! Buy at http://shopping.yahoo.com or bid at http://auctions.yahoo.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message