From owner-freebsd-current  Sun Jan 12 13:18:49 1997
Return-Path: <owner-current>
Received: (from root@localhost)
          by freefall.freebsd.org (8.8.4/8.8.4) id NAA22676
          for current-outgoing; Sun, 12 Jan 1997 13:18:49 -0800 (PST)
Received: from rocky.mt.sri.com (rocky.mt.sri.com [206.127.76.100])
          by freefall.freebsd.org (8.8.4/8.8.4) with ESMTP id NAA22670;
          Sun, 12 Jan 1997 13:18:45 -0800 (PST)
Received: (from nate@localhost) by rocky.mt.sri.com (8.7.5/8.7.3) id OAA22215; Sun, 12 Jan 1997 14:18:14 -0700 (MST)
Date: Sun, 12 Jan 1997 14:18:14 -0700 (MST)
Message-Id: <199701122118.OAA22215@rocky.mt.sri.com>
From: Nate Williams <nate@mt.sri.com>
To: Christoph Kukulies <kuku@gilberto.physik.rwth-aachen.de>
Cc: mpp@freefall.freebsd.org (Mike Pritchard), joerg_wunsch@uriah.heep.sax.de,
        freebsd-current@freefall.freebsd.org
Subject: Re: a last word on last
In-Reply-To: <199701122003.VAA01205@gilberto.physik.rwth-aachen.de>
References: <199701121901.LAA11130@freefall.freebsd.org>
	<199701122003.VAA01205@gilberto.physik.rwth-aachen.de>
Sender: owner-current@FreeBSD.ORG
X-Loop: FreeBSD.org
Precedence: bulk

> > > > But piping the last command to anything, be it 'more' or 'head'
> > > > gives totally garbled output. Fields contain garbage and seem to be
> > > > shifted by one postition.

> > I would suggest zeroing out wtmp and seeing what happens.
> 
> Well, I zeroed wtmp/utmp several times in the past and the problem
> came back. This may because of the various changes to the wtmp/utmp thing.

Are you using an older version of xdm or xterm.  If they haven't been
recompiled they will create (now bogus) entries.


Nate