From owner-freebsd-bugs Mon Jul 23 9: 0: 9 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 D354C37B405 for ; Mon, 23 Jul 2001 09:00:03 -0700 (PDT) (envelope-from gnats@FreeBSD.org) Received: (from gnats@localhost) by freefall.freebsd.org (8.11.4/8.11.4) id f6NG03D78052; Mon, 23 Jul 2001 09:00:03 -0700 (PDT) (envelope-from gnats) Date: Mon, 23 Jul 2001 09:00:03 -0700 (PDT) Message-Id: <200107231600.f6NG03D78052@freefall.freebsd.org> To: freebsd-bugs@FreeBSD.org Cc: From: Mike Barcroft Subject: Re: kern/15478: incorrect utmp/wtmp records update upon connection being interrupted Reply-To: Mike Barcroft 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: Mike Barcroft To: freebsd-gnats-submit@FreeBSD.org Cc: Subject: Re: kern/15478: incorrect utmp/wtmp records update upon connection being interrupted Date: Mon, 23 Jul 2001 12:11:08 -0400 Adding to Audit-Trail. ----- Forwarded message from Igor Roshchin ----- Delivered-To: mike@freebsd.org Date: Mon, 23 Jul 2001 02:06:33 -0400 (EDT) From: Igor Roshchin To: freebsd-bugs@FreeBSD.org, mike@FreeBSD.org Subject: Re: kern/15478: incorrect utmp/wtmp records update upon connection being interrupted In-Reply-To: <200107211820.f6LIKsA19064@freefall.freebsd.org> > From mike@FreeBSD.org Sat Jul 21 14:24:59 2001 > Date: Sat, 21 Jul 2001 11:20:54 -0700 (PDT) > From: > To: str@giganda.komkon.org, mike@FreeBSD.org, freebsd-bugs@FreeBSD.org > Subject: Re: kern/15478: incorrect utmp/wtmp records update upon connection being interrupted > > Synopsis: incorrect utmp/wtmp records update upon connection being interrupted > > State-Changed-From-To: open->feedback > State-Changed-By: mike > State-Changed-When: Sat Jul 21 11:20:43 PDT 2001 > State-Changed-Why: > > Does this problem still occur in newer versions of FreeBSD, > such as 4.3-RELEASE? > > http://www.FreeBSD.org/cgi/query-pr.cgi?pr=15478 > Although I have not been paying close attention to this problem recently, a quick look at a wtmp file shows that it still happens on a 4.3-RELEASE box. Igor ----- End forwarded message ----- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-bugs" in the body of the message