kinit locking up
Russ Allbery
rra at stanford.edu
Sat Dec 10 20:36:06 EST 2005
Jon DeVree <jadevree at mtu.edu> writes:
> futex(0x804d2f4, FUTEX_WAIT, 2, NULL) = -1 EINTR (Interrupted system
> call)
> Of course I Ctrl+C'd kinit after a few seconds.
Well, huh.
Of course, I can't manage to reproduce this (or I wouldn't have uploaded
the new Kerberos packages to Debian until I got to the bottom of it). I'm
rather unclear as to what could be going on, or why it would be sensitive
to whether or not you gave your principal name on the command line.
Out of curiousity, if it's easy for you, could you install the kstart
package and try obtaining a ticket with k5start? It should work basically
like kinit, but it's an independent implementation. That should isolate
whether it's some sort of library problem or possibly a problem in kinit
itself.
--
Russ Allbery (rra at stanford.edu) <http://www.eyrie.org/~eagle/>
More information about the Kerberos
mailing list