Debugging kdcs and signals

Sam Hartman hartmans at MIT.EDU
Sat Sep 10 16:36:38 EDT 2011

>>>>> "Greg" == Greg Hudson <ghudson at MIT.EDU> writes:
    Greg> The one case where I've seen something like this is when I'm
    Greg> debugging a or dejagnu test case and I let the
    Greg> script terminate.  For example, if I use'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.)

More information about the krbdev mailing list