From owner-freebsd-current Wed May 20 08:23:25 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id IAA16064 for freebsd-current-outgoing; Wed, 20 May 1998 08:23:25 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from austin.polstra.com (austin.polstra.com [206.213.73.10]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id IAA16058 for ; Wed, 20 May 1998 08:23:22 -0700 (PDT) (envelope-from jdp@austin.polstra.com) Received: from austin.polstra.com (jdp@localhost) by austin.polstra.com (8.8.8/8.8.8) with ESMTP id IAA24397; Wed, 20 May 1998 08:23:00 -0700 (PDT) (envelope-from jdp) Message-Id: <199805201523.IAA24397@austin.polstra.com> To: hometeam@techpower.net Subject: Re: wtmp In-Reply-To: References: Organization: Polstra & Co., Seattle, WA Cc: current@FreeBSD.ORG Date: Wed, 20 May 1998 08:23:00 -0700 From: John Polstra Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In article , Jt wrote: > 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. The format of the wtmp file changed between 2.2 and -current, to accomodate the longer user names now supported in -current. You still have some old program that is writing wtmp in the old format. The usual perpetrators are sshd and xterm. Rebuild both of those, and chances are that the problem will be solved. You'll probably need to clean out wtmp to get a fresh start. -- John Polstra jdp@polstra.com John D. Polstra & Co., Inc. Seattle, Washington USA "Self-knowledge is always bad news." -- John Barth To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message