From owner-freebsd-current Tue May 19 16:59:58 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id QAA21267 for freebsd-current-outgoing; Tue, 19 May 1998 16:59:58 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from techpower.net (hometeam@techpower.net [205.133.231.1]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id QAA21232 for ; Tue, 19 May 1998 16:59:41 -0700 (PDT) (envelope-from hometeam@techpower.net) Received: from localhost (hometeam@localhost) by techpower.net (8.8.8/8.8.8) with SMTP id PAA02957; Tue, 19 May 1998 15:59:37 -0400 (EDT) (envelope-from hometeam@techpower.net) Date: Tue, 19 May 1998 15:59:37 -0400 (EDT) From: Jt To: Nathan Dorfman cc: current@FreeBSD.ORG Subject: Re: wtmp In-Reply-To: <19980519182803.A3370@rtfm.net> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG May 17 1998 I did make a big jump from 2.2.6 stable. I had a few minor problems , This I just noticed today. It like the wtmp is fragmented or something. hometeam@techpower.net On Tue, 19 May 1998, Nathan Dorfman wrote: > On Tue, May 19, 1998 at 12:03:13PM -0400, Jt wrote: > > > > Whats wrong with wtmp in current after lusers logout it still shows > > connected. ( last luser ) ? > > I saw this behaviour once with a telnet login. However, it was very > long ago, back in April with April's tree. How current is your > -current? > > > hometeam@techpower.net > > -- > ________________ ______________________________ > / Nathan Dorfman \ / "Nietzsche is dead." - God \ > / nathan@rtfm.net \/ http://www.FreeBSD.org/ \ > / finger for PGP key \ FreeBSD 2.2.6 is now out! \ > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message