[1666] in SIPB_Linux_Development
login takes me 13 minutes
daemon@ATHENA.MIT.EDU (Joanne M Mikkelson)
Sat May 3 16:57:09 1997
Date: Sat, 3 May 1997 16:56:46 -0400 (EDT)
From: jmmikkel@MIT.EDU (Joanne M Mikkelson)
To: linux-dev@MIT.EDU
So I painfully installed RedHat and I'll spare the details of the
hours of network futzing I had to do... For some reason emacs
wouldn't start up without the network, either.
Anyway, the real point is that then I took my computer home, where I
am evidently one of the few who doesn't have a network. Of course, I
had neglected to remove networking stuff from the startup before I
brought the computer home.
Hence I would like to remind people that gettime NEVER times out, and
hence I had to boot single-user if I wanted to ever get booted. Also,
zhm doesn't time out either. Could this be fixed? Is there some good
reason why gettime doesn't time out? It's really annoying. I am told
gettime has been this way for years.
But *even* more annoying (and this seems specific to the install) was
the fact that upon booting my computer, I discovered that it takes me
13 minutes to log in. No, it's not my dotfiles. No, I'm not kidding,
*13* minutes, at least.
I don't know what is happening that causes my login to take 13
minutes, but I know it's all in /bin/login because 13 minutes is
plenty of time to observe that it's all being spent by
/bin/login. Here's what it says, after many minutes (presumably 5
of them ;-) :
Login timed out after 300 seconds.
This struck me as weird (since my local password had been typed
correctly and I had hit return), especially since after this was
printed, nothing happened (i.e. login didn't actually die). Several
minutes later, it printed:
Kerberos error: Can't send request (send_to_kdc)
This did not strike me as weird since that's what it printed before I
reinstalled, although before I installed it took less than a second
to print that, after which it went on with my login. But not any
more! Even after the kerberos error, I had to wait a couple more
minutes for it to say (which it normally does, but more quickly):
Warning: no Kerberos tickets obtained.
And *then* it gave me a shell...
Needless to say, I was not happy with the prospect of it taking me 13
minutes to log in when it should take mere seconds. I copied over my
old login binary and it fared no better! Clearly there is something
else going on that I'm missing. What is it? ldd thinks both binaries
only use libc, so it's not a change in the kerberos library...
Then I tried using /bin/login.redhat, since without kerberos it ought
to be able to deal, but NO, it bombed out too. It printed "Login
incorrect" *four* times after I typed my username (the password was
evidently unnecessary), returned to the login prompt, and syslogged
the following:
May 1 18:25:10 dans-le-carre login: 1 FAILED LOGINS FROM (null) FOR
jmmikkel, Authentication failure
May 1 18:25:10 dans-le-carre login: 2 FAILED LOGINS FROM (null) FOR
(null), Authentication failure
May 1 18:25:10 dans-le-carre login: 3 FAILED LOGINS FROM (null) FOR
(null), Authentication failure
May 1 18:25:10 dans-le-carre login: FAILED LOGIN SESSION FROM (null)
FOR (null), Authentication failure
Needless to say, I figured a 13-minute login was better than none at
all, and I put the athena login back.
Can anyone help me here? On the far end of a 14.4k phone line, I'm
not in the slightest bit psyched about ftp'ing over the linux-athena
login sources and fighting with it, with the small hope that I'll
find out what's going on (ha ha, I have a thesis to write
instead). Really all I could hope from that was the find out what it
was waiting on, since the older binary has the same problem.
Finally, I want to just know - is it our policy to assume everyone's
always on the net? If it is, I should think it would be kind to say
so in a footnote on the docs or something. If it's not our policy, I
should think we should try booting a fresh install without net before
we consider the testing to be done...
I suppose I should have tried without the net before bringing my
computer home but I must say I wasn't expecting quite *this*
problem...
Joanne
PS - root logins don't take 13 minutes, only (:-P) about one or two.
