From: "Joshua" <jle@post.com>
To: <cygwin@cygwin.com>
Subject: login 1.4-2 LASTLOG file mismatch
Date: Fri, 04 Jan 2002 13:34:00 -0000 [thread overview]
Message-ID: <000701c19567$6df7a1c0$58995b8f@irngtx.tel.gte.com> (raw)
All,
I think I've found a small bug in the login program code versus the man
page regarding the last login feature. The man page indicates that the file
necessary for storing the last login information is /var/log/lastlog, and
this file was actually created with zero length automatically. But the code
references the file location as /usr/adm/lastlog, which is not created
automatically.
When I created a zero length file /usr/adm/lastlog, the login program
now shows the last login date, time, and source. Now, after the first use
of the /usr/adm/lastlog file, it's size grew to 3,048,420 bytes! What's in
that file? Is that normal?
As a side question, when I compile Cygwin programs locally, they seem to
be much larger than the binaries installed by setup.exe. For example, login
installed by setup.exe is 11,776 bytes; the login that I compiled myself is
44,945 bytes. I made no changes whatsoever to the source code, and used the
makefile that came in the tarball. In checking the archives, I saw one
cryptic reference to using 'strip' but I don't really understand that
reference. BCNU//jle
--
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/
next reply other threads:[~2002-01-04 21:34 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-01-04 13:34 Joshua [this message]
2002-01-05 13:20 ` Gerrit P. Haase
2002-01-05 13:22 ` Corinna Vinschen
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='000701c19567$6df7a1c0$58995b8f@irngtx.tel.gte.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).