From owner-freebsd-current Thu Dec 12 23:00:50 1996 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.4/8.8.4) id XAA25663 for current-outgoing; Thu, 12 Dec 1996 23:00:50 -0800 (PST) Received: from grackle.grondar.za (DU8JqcnXh+DfNzHk2Uv1ZzS2dFwpe254@grackle.grondar.za [196.7.18.131]) by freefall.freebsd.org (8.8.4/8.8.4) with ESMTP id XAA25657 for ; Thu, 12 Dec 1996 23:00:39 -0800 (PST) Received: from grackle.grondar.za (XtTiv40jbychYmD8XgtXAxN27z1x6pzL@localhost [127.0.0.1]) by grackle.grondar.za (8.8.4/8.8.4) with ESMTP id IAA04156; Fri, 13 Dec 1996 08:59:27 +0200 (SAT) Message-Id: <199612130659.IAA04156@grackle.grondar.za> To: Christoph Kukulies cc: freebsd-current@freefall.freebsd.org Subject: Re: wtmp Date: Fri, 13 Dec 1996 08:59:21 +0200 From: Mark Murray Sender: owner-current@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk Christoph Kukulies wrote: > > 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 ^^^^^^^ Build a new kernel and reboot. > This is on a yesterday's -current machine. Not the kernel! M -- Mark Murray PGP key fingerprint = 80 36 6E 40 83 D6 8A 36 This .sig is umop ap!sdn. BC 06 EA 0E 7A F2 CE CE