uaa1006@dircon.co.uk (Peter Miles) (05/23/91)
I'm running SCO UNIX 386 v3.2.2. I've noticed that the 'last'
command doesn't seem to be very accurate. When I run it, it
shows at least one user who has been logged on (supposedly)
for over 2 days on a particular TTY. Even though the user hasn't
been logged in for that long, and other users have logged in
on the same tty.
Here's an excerpt from the last command...
User Line Device PID Login time Elapsed Time Comments
pmiles A03 ttyA03 23974 Wed May 22 09:28 00:09
pmiles A02 ttyA02 23455 Wed May 22 08:58 00:10
alanb A04 ttyA04 24589 Wed May 22 08:16 00:03
pmiles A01 ttyA01 24545 Wed May 22 00:47 00:00
alanb A03 ttyA04 24533 Tue May 21 23:57 00:04 **
pmiles A01 ttyA01 23955 Tue May 21 23:01 00:53
pmiles A03 ttyA03 23748 Tue May 21 22:30 00:00 **
cathy A01 ttyA01 23535 Tue May 21 21:33 00:04
pmiles A03 ttyA03 22757 Tue May 21 21:21 00:19 **
mike A01 ttyA01 22457 Tue May 21 21:09 00:23
mike A04 ttyA04 21960 Tue May 21 20:49 00:32
johnh A02 ttyA02 20761 Tue May 21 20:30 00:48
alanb A03 ttyA03 9578 Tue May 21 01:11 2d 10:14 logged in **
mike A01 ttyA01 8862 Mon May 20 22:51 00:32
As you can see (from the lines marked **) several people have
been logged in on ttyA03, but last still shows that 'alanb'
is logged in and has been for over 2 days.
Is there a more accurate way of measuring the login times and
length of login for users? I need this information to be accurate
to the nearest minute.
-- Pete
--
Pete Miles uaa1006@dircon.co.uk
...ukc!dircon!uaa1006