Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm
List-Subscribe: <mailto:cygwin-subscribe AT cygwin DOT com>
List-Archive: <http://sources.redhat.com/ml/cygwin/>
List-Post: <mailto:cygwin AT cygwin DOT com>
List-Help: <mailto:cygwin-help AT cygwin DOT com>, <http://sources.redhat.com/ml/#faqs>
Sender: cygwin-owner AT cygwin DOT com
Delivered-To: mailing list cygwin AT cygwin DOT com
Message-ID: <000501c1965b$97980fc0$02f5ee0c@attbi.com>
From: "Joshua" <jle AT post DOT com>
To: <cygwin AT cygwin DOT com>
Subject: Fw: login 1.4-2 LASTLOG file mismatch
Date: Sat, 5 Jan 2002 20:41:06 -0600
MIME-Version: 1.0
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: 7bit
X-Priority: 3
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook Express 5.50.4522.1200
X-MimeOLE: Produced By Microsoft MimeOLE V5.50.4522.1200

    Forwarding to the list for the explanation of the file size of lastlog.
BCNU//jle

----- Original Message -----
From: "Mark Bradshaw" <bradshaw AT staff DOT crosswalk DOT com>
To: "'Joshua'" <jle AT post DOT com>
Sent: Friday, 04 January, 2002 15:40
Subject: RE: login 1.4-2 LASTLOG file mismatch


<<SNIP>>

> Lastlog is a bit strange.  Instead of logging the UID of the information
> being stored, it indexes into the file a certain amount to denote the UID.
> For instance, if the information block that's stored at login takes up 256
> bytes, when a user with a UID of 400 logs in login will go into the file
> 400*256 bytes to find the appropriate spot to store that block of
> information.  Seems like a bad way to go, but there you are.  That's why
it
> suddenly balooned.  It created a whole bunch of empty space just to put
the
> your login information in the "proper" place.
>



--
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple
Bug reporting:         http://cygwin.com/bugs.html
Documentation:         http://cygwin.com/docs.html
FAQ:                   http://cygwin.com/faq/