[17157] in Kerberos_V5_Development
Re: Debugging kdcs and signals
daemon@ATHENA.MIT.EDU (Greg Hudson)
Sat Sep 10 18:03:58 2011
From: Greg Hudson <ghudson@mit.edu>
To: Sam Hartman <hartmans@mit.edu>
In-Reply-To: <tslsjo4t9rd.fsf@mit.edu>
Date: Sat, 10 Sep 2011 18:03:48 -0400
Message-ID: <1315692228.718.123.camel@t410>
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
On Sat, 2011-09-10 at 16:36 -0400, Sam Hartman wrote:
> This is exactly my issue, thanks.
> I had not done this type of debugging with k5test before. Sorry about
> the false alarm.
I'm changing k5test.py on trunk so that it waits for input before
killing daemons if it was run with any interactive options (--debug,
--stop-after, etc.). No reason for anyone else to lose productive time
to this.
_______________________________________________
krbdev mailing list krbdev@mit.edu
https://mailman.mit.edu/mailman/listinfo/krbdev
