From: "Joshua" <jle@post.com>
To: <cygwin@cygwin.com>
Subject: Fw: login 1.4-2 LASTLOG file mismatch
Date: Sat, 05 Jan 2002 18:41:00 -0000 [thread overview]
Message-ID: <000501c1965b$97980fc0$02f5ee0c@attbi.com> (raw)
Forwarding to the list for the explanation of the file size of lastlog.
BCNU//jle
----- Original Message -----
From: "Mark Bradshaw" <bradshaw@staff.crosswalk.com>
To: "'Joshua'" <jle@post.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/
reply other threads:[~2002-01-06 2:41 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to='000501c1965b$97980fc0$02f5ee0c@attbi.com' \
--to=jle@post.com \
--cc=cygwin@cygwin.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).