From owner-freebsd-questions Fri Aug 20 7:50:20 1999 Delivered-To: freebsd-questions@freebsd.org Received: from vax1.baker.ie (VAX1.baker.IE [194.125.50.91]) by hub.freebsd.org (Postfix) with SMTP id 3E37C14BE5 for ; Fri, 20 Aug 1999 07:50:17 -0700 (PDT) (envelope-from cillian@baker.ie) Received: from baker.ie ([194.125.50.55]) by vax1.baker.ie with ESMTP; Fri, 20 Aug 1999 15:25:19 +0100 Message-ID: <37BD6EE5.390931D5@baker.ie> Date: Fri, 20 Aug 1999 16:06:13 +0100 From: Cillian Sharkey X-Mailer: Mozilla 4.51 [en] (X11; I; FreeBSD 3.2-STABLE i386) X-Accept-Language: en MIME-Version: 1.0 To: fr@icsmedia.de Cc: questions@freebsd.org Subject: Re: Strange characters of "last" after upgrade to 3.2 Release References: <01BACE0D6FA9D21198CC00A0C94D131D0FF7C3@note.icsmedia.de> Content-Type: text/plain; charset=iso-8859-1 Content-Transfer-Encoding: 8bit Sender: owner-freebsd-questions@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > The Problem ist not the format of the old (from 2.2.2) entries of the wtmp > and utmp. The new ones (from 3.2) are corrupt!! > > Regards, > > Frank > > P.S I´ve also set the size of wtmp and utmp to zero but without success Hmm..that must mean that the entries created by your new 3.2 binaries must be corrupting the file (even if it was nuked and had to be re-created) Or perhaps, you still have some 2.x stuff floating around that is the cause ? in a similar situation to this I found out ssh was the culprit..a quick recompile of it did the trick Hope this helps, - Cillian To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-questions" in the body of the message