From owner-freebsd-questions Tue Oct 12 13:55:21 1999 Delivered-To: freebsd-questions@freebsd.org Received: from logisticsoftware.co.nz (logisticsoftware.co.nz [202.37.163.1]) by hub.freebsd.org (Postfix) with ESMTP id 559FB14FC1 for ; Tue, 12 Oct 1999 13:55:16 -0700 (PDT) (envelope-from jonc@logisticsoftware.co.nz) Received: (from jonc@localhost) by logisticsoftware.co.nz (8.9.3/8.9.3) id JAA10554; Wed, 13 Oct 1999 09:54:37 +1300 (NZDT) Date: Wed, 13 Oct 1999 09:54:37 +1300 (NZDT) From: Jonathan Chen To: lamont@abstractsoft.com Cc: questions@FreeBSD.ORG Subject: Re: 3.X last? In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-questions@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Tue, 12 Oct 1999, Sean T. Lamont .lost. wrote: > On Wed, 13 Oct 1999, Jonathan Chen wrote: > > > On Tue, 12 Oct 1999, Sean T. Lamont .lost. wrote: > > > > > > > > It seems that the wtmp format has changed as of 3.0 but that the > > > 'last' program hasn't. As a result, it's largely useless. > > > > > > Has anyone fixed this problem, or is it up to me? > > > > Zap /var/log/wtmp. ie: > > > > cp /dev/null /var/log/wtmp > > > > It'll work from then on. > > Actually, it didn't. > Odd. The wtmp format underwent a change on transition from 2.2.x to 3.x. It works fine on the 3.1, 3.2 and 3.3 machines here. Are you sure you're running the correct/latest last(1)? Also, any old programs that modify wtmp will also need to recompiled and reinstalled (eg: screen), so that they `know' about the wtmp changes. Are you running any 2.2 a.out stuff on your machine? Jonathan Chen -------------------------------------------------------------------- The Internet: an empirical test of the idea that a million monkeys banging on a million keyboards can produce Shakespeare To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-questions" in the body of the message