[17155] in Kerberos_V5_Development
Re: Debugging kdcs and signals
daemon@ATHENA.MIT.EDU (Sam Hartman)
Sat Sep 10 16:36:45 2011
From: Sam Hartman <hartmans@mit.edu>
To: Greg Hudson <ghudson@mit.edu>
Date: Sat, 10 Sep 2011 16:36:38 -0400
In-Reply-To: <1315686563.718.119.camel@t410> (Greg Hudson's message of "Sat,
10 Sep 2011 16:29:23 -0400")
Message-ID: <tslsjo4t9rd.fsf@mit.edu>
MIME-Version: 1.0
Cc: "krbdev@mit.edu" <krbdev@mit.edu>
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Errors-To: krbdev-bounces@mit.edu
>>>>> "Greg" == Greg Hudson <ghudson@MIT.EDU> writes:
Greg> The one case where I've seen something like this is when I'm
Greg> debugging a k5test.py or dejagnu test case and I let the
Greg> script terminate. For example, if I use k5test.py's
Greg> --stop-before=N, attach to the KDC, and then let the script
Greg> continue, the client program will typically time out, causing
Greg> the script to fail out and kill the KDC. I work around this
Greg> by using --stop-after=N in addition to --stop-before=N. I
Greg> would guess that this isn't the case you're seeing, but I'm
Greg> mentioning it just in case.
This is exactly my issue, thanks.
I had not done this type of debugging with k5test before. Sorry about
the false alarm.
(I'm debugging RFC 6112 pkinit fixes.)
_______________________________________________
krbdev mailing list krbdev@mit.edu
https://mailman.mit.edu/mailman/listinfo/krbdev
