Bug#2328: rlogind can cause finger to report wrong idle time
When rlogind logs you in with no password, no data is read from the
pty that is used until you type your first command. This means that
the read timestamp on the pty slave from the previous session is left
in place, so that finger &c think you've been idle for a very long
The solution is, I believe, to call utime() on the pty slave at some
PS: There are numerous other utmp problems with the system as a whole.