Debugging kdcs and signals
ghudson at MIT.EDU
Sat Sep 10 18:03:48 EDT 2011
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
More information about the krbdev