Subject: Re: Text form of wtmp
To: None <>
From: Ignatios Souvatzis <>
List: tech-userlevel
Date: 02/16/2005 14:18:27
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
Content-Transfer-Encoding: quoted-printable

On Wed, Feb 16, 2005 at 02:12:49PM +0200, Valentin Nechayev wrote:
>  Tue, Feb 15, 2005 at 16:40:44, greywolf wrote about "Re: Text form of wt=
> VS>> Why can't we use text file for wtmp? wtmp is just a log file, that is
> VS>> similar to other log files in system. We need to fix only last and ac
> VS>> programmes and libutil routines to work with text wtmp. I understand,
> VS>> that analyzing of wtmp records would be more complex, but wtmp would=
> VS>> in human readable form. And we would not need to trim hostname, beca=
> VS>> even in wtmpx the maximum hostname length is 256 bytes, and real max
> VS>> length is 1024 bytes.
> > wtmp is a binary file with fixed length records because it makes for mu=
> > faster processing.
> Does faster processing really gives anything important in that particular
> case? There are too few tasks which require automatic reading of wtmp.
> First law of optimization says "Don't optimize unless really needed".

I hope you're aware how those records are searched, displayed, and updated.
E.g. lastlog is mostly searched _backwards_. Not good without record sizes=
at the end of the line... or fixed sizes records.

Also, you should consider that not all machines are single-effective-user
desktop machines.


Content-Type: application/pgp-signature
Content-Disposition: inline

Version: GnuPG v1.2.3 (NetBSD)