From owner-freebsd-bugs Thu Oct 11 7: 0: 7 2001 Delivered-To: freebsd-bugs@hub.freebsd.org Received: from freefall.freebsd.org (freefall.FreeBSD.org [216.136.204.21]) by hub.freebsd.org (Postfix) with ESMTP id 7702137B403 for ; Thu, 11 Oct 2001 07:00:02 -0700 (PDT) Received: (from gnats@localhost) by freefall.freebsd.org (8.11.4/8.11.4) id f9BE02i39682; Thu, 11 Oct 2001 07:00:02 -0700 (PDT) (envelope-from gnats) Date: Thu, 11 Oct 2001 07:00:02 -0700 (PDT) Message-Id: <200110111400.f9BE02i39682@freefall.freebsd.org> To: freebsd-bugs@FreeBSD.org Cc: From: "Yar Tikhiy" Subject: Re: kern/15478: incorrect utmp/wtmp records update upon connection being interrupted Reply-To: "Yar Tikhiy" Sender: owner-freebsd-bugs@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.org The following reply was made to PR kern/15478; it has been noted by GNATS. From: "Yar Tikhiy" To: , Cc: Subject: Re: kern/15478: incorrect utmp/wtmp records update upon connection being interrupted Date: Thu, 11 Oct 2001 17:57:08 +0400 As I can see, it's hardly a FreeBSD problem. It's the consequence of some applications (e.g. xterm, rxvt, screen) modifying utmp bogusly. Rxvt and xterm just can't clean up if killed unconditionally. As for screen, it does a Very Bad Thing: It takes a user record out of utmp at startup. Of course, /sbin/init then won't add a logout record to wtmp if the session gets aborted. If I were in your shoes, I'd report that to the author of screen. The instant cure is to remove the set-uid bit from the programs so they won't mess utmp up. If you don't mind, I'd rather close this PR since it has to do nothing with FreeBSD. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-bugs" in the body of the message