[25095] in Kerberos
Re: kinit locking up
daemon@ATHENA.MIT.EDU (Russ Allbery)
Sat Dec 10 21:50:48 2005
From: Russ Allbery <rra@stanford.edu>
Date: Sat, 10 Dec 2005 17:36:06 -0800
Message-ID: <87k6ech0u1.fsf@windlord.stanford.edu>
To: kerberos@mit.edu
Errors-To: kerberos-bounces@mit.edu
Jon DeVree <jadevree@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@stanford.edu) <http://www.eyrie.org/~eagle/>
________________________________________________
Kerberos mailing list Kerberos@mit.edu
https://mailman.mit.edu/mailman/listinfo/kerberos
