On Mar 29,  8:42pm, dive@endersgame.net (Sean Davis) wrote:
-- Subject: Re: lastlogx inappropriate format?

| On Tue, Mar 29, 2005 at 02:26:42PM -0500, Christos Zoulas wrote:
| > On Mar 29,  9:00pm, jmmv84@gmail.com ("Julio M. Merino Vidal") wrote:
| > -- Subject: Re: lastlogx inappropriate format?
| > 
| > | Before doing this:
| > | 
| > | [sun jmmv] $ ls -l /var/log/lastlog* 
| > | -rw-rw-r--  1 root  wheel  28028 Mar 29 20:58 /var/log/lastlog
| > | -rw-rw-r--  1 root  wheel      0 Mar 19 19:21 /var/log/lastlogx
| > | 
| > | So these commands will have no effect (the file is already empty and
| > | with the correct permissions).
| > | 
| > | FWIW, and as I said, this was on a machine where 3.0_BETA was installed
| > | from scratch.  Just after the installation, at the very first login,
| > | I could see that message popping up on the screen.  So there seems to be
| > | a problem somewhere.
| > 
| > That error is new [i.e. lastlogx write failures were silent before].
| > I am running current, and I can see my lastlogx growing. This is strange.
| 
| I saw this both on a 3.99.1 sparc64 and a 3.0_BETA sparc64. rm;touch did
| *not* fix it. Removing the file and letting login create it on its own did.
| After that, I never saw the error again, and lastlogx grows as expected.

Yes, I fixed this by making hash.c in libc able to create a db on top of
a 0 length file. The fix is on the request queue for 3.0.

christos