Date: Fri, 20 Aug 1999 18:54:32 +0100 From: Ben Smithurst <ben@scientia.demon.co.uk> To: Cillian Sharkey <cillian@baker.ie> Cc: fr@icsmedia.de, questions@freebsd.org Subject: Re: Strange characters of "last" after upgrade to 3.2 Release Message-ID: <19990820185432.A17746@lithium.scientia.demon.co.uk> In-Reply-To: <37BD6EE5.390931D5@baker.ie> References: <01BACE0D6FA9D21198CC00A0C94D131D0FF7C3@note.icsmedia.de> <37BD6EE5.390931D5@baker.ie>
next in thread | previous in thread | raw e-mail | index | archive | help
Cillian Sharkey wrote:
>> 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 Ive 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
If you haven't rebuilt X, I think that will also be using the old
format. (xterm, or some part of X, logs an entry in utmp.)
--
Ben Smithurst | PGP: 0x99392F7D
ben@scientia.demon.co.uk | key available from keyservers and
| ben+pgp@scientia.demon.co.uk
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-questions" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?19990820185432.A17746>