From owner-freebsd-current Thu Dec 12 22:14:27 1996 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.4/8.8.4) id WAA22580 for current-outgoing; Thu, 12 Dec 1996 22:14:27 -0800 (PST) Received: from Campino.Informatik.RWTH-Aachen.DE (campino.Informatik.RWTH-Aachen.DE [137.226.116.240]) by freefall.freebsd.org (8.8.4/8.8.4) with ESMTP id WAA22571 for ; Thu, 12 Dec 1996 22:14:24 -0800 (PST) Received: from gilberto.physik.rwth-aachen.de (gilberto.physik.rwth-aachen.de [137.226.31.2]) by Campino.Informatik.RWTH-Aachen.DE (RBI-Z-5/8.6.12) with ESMTP id HAA13081 for ; Fri, 13 Dec 1996 07:16:05 +0100 (MET) Received: (from kuku@localhost) by gilberto.physik.rwth-aachen.de (8.8.3/8.6.9) id HAA04492 for freebsd-current@freefall.cdrom.com; Fri, 13 Dec 1996 07:29:05 +0100 (MET) Date: Fri, 13 Dec 1996 07:29:05 +0100 (MET) From: Christoph Kukulies Message-Id: <199612130629.HAA04492@gilberto.physik.rwth-aachen.de> To: freebsd-current@freefall.FreeBSD.org Subject: wtmp Sender: owner-current@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk I'm aware that some commands (last, w) were broken due to the wtmp changes recently but what is the way to handle this correctly on an updated machine? I deleted /var/log/wtmp and did a touch /var/log/wtmp. I still get # w 7:09AM up 48 days, 12:07, 3 users, load averages: 0.00, 0.00, 0.00 USER TTY FROM LOGIN@ IDLE WHAT &r­2ttyv2 - 01Jan70 4:07 - ttyp0 toots Thu09PM 4:07 - kuku p1 kuku-home 7:07AM - w # This is on a yesterday's -current machine. --Chris Christoph P. U. Kukulies kuku@gil.physik.rwth-aachen.de