Date: Sat, 11 Jan 1997 09:29:00 -0600 (CST) From: Greg Lehey <grog@lemis.de> To: kuku@gilberto.physik.rwth-aachen.de Cc: FreeBSD-current@FreeBSD.ORG (FreeBSD current users) Subject: Re: last command - wtmp changes? Message-ID: <199701111529.JAA00366@papillon.lemis.de> In-Reply-To: <199701071116.MAA05806@gilberto.physik.rwth-aachen.de> from Christoph Kukulies at "Jan 7, 97 12:16:40 pm"
next in thread | previous in thread | raw e-mail | index | archive | help
Christoph Kukulies writes: >> As Christoph Kukulies wrote: >> >>> Strange, when I login in as user 'kuku' in one of my machines >>> I'm seeing the following picture: >>> >>> bach> last kuku | head >>> kuku ttyp0 137.226.31.18 Mon Jan 6 10:10 still logged in >>> kuku ttyp0 137.226.31.18 Mon Jan 6 10:08 - 10:09 (00:00) >>> kuku ttyp0 137.226.31.18 Mon Jan 6 10:07 - 10:08 (00:01) >>> kuku ttyp0 gilberto Sat Jan 4 21:42 - 21:43 (00:00) >>> kuku ttyp0 137.226.145.27 Fri Jan 3 10:12 still logged in >>> ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ >>> This connection doesn't exist. >> >> That only means the connection broke, but telnetd (or whatever it has >> been) has ``forgotten'' to write the logout entry in wtmp. > > Well, I know of these situations sometimes happening but what I meant > was: Why does this 'broken' connection in last 'kuku' only show when > I'm logged in as user kuku and does not show up in the output of > the last command when I give it from another user account. > > Well, maybe it's not worth and has been some transient problem. > It's gone anyway now after I rebooted yesterday. It doesn't always go away that easily. I'm currently travelling with my notebook, and I find: === grog@papillon (/dev/ttyp1) ~ 1 -> last grog grog ttyp0 Wed Dec 31 18:00 still logged in freebie:0.0 grog Å2~ Sat Sep 23 06:24 still logged in unix:0.0 grog )L¼2ttyp0 Wed Dec 31 18:00 still logged in unix:0.0 grog k¹2~ Sat Sep 23 06:24 - 18:00 (12:36) unix:0.0 grog )¸2ttyp1 Wed Dec 31 18:00 - shutdown (9849+15:44) I shut freebie down yesterday before leaving, and I'm pretty sure I'm not connected to any other machine right now. And, of course, I've rebooted several times since then. *And* I didn't even have the machine on September 23. Note also the amusing system names. I'm guessing that last doesn't check for error conditions on resolver lookups. The time at the end of the last line is also amusing. At a rough guess, it goes back to the Epoch. Looks like there's a minefield of bugs for some interested party to clean up here. Greg
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?199701111529.JAA00366>