From owner-freebsd-current Thu Mar 5 23:57:09 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id XAA07335 for freebsd-current-outgoing; Thu, 5 Mar 1998 23:57:09 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from pop.uniserve.com (pop.uniserve.com [204.244.156.3]) by hub.freebsd.org (8.8.8/8.8.8) with SMTP id XAA07314 for ; Thu, 5 Mar 1998 23:57:05 -0800 (PST) (envelope-from tom@uniserve.com) Received: from shell.uniserve.com [204.244.186.218] by pop.uniserve.com with smtp (Exim 1.82 #4) id 0yArk0-0000YB-00; Thu, 5 Mar 1998 23:40:24 -0800 Date: Thu, 5 Mar 1998 23:40:20 -0800 (PST) From: Tom To: "Daniel O'Connor" cc: current@FreeBSD.ORG Subject: Re: utmp problem In-Reply-To: <199803060715.RAA16103@cain.gsoft.com.au> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Fri, 6 Mar 1998, Daniel O'Connor wrote: > I can't pinpoint _when_ it misbehaves, which is pretty useless :) > I was just wondering if any one has seen this problem before. See the archives for lots of reports of this. You have some old software which is screwing it up. The username length was changed from 8 to 16 a long time ago, and unfortunately, due to the silly way wtmp/utmp is handled, all software which touches these files needs to be re-compiled. Tom To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message