The mysterious death of kprop when running incremental propagtion

Mon Mar 31 20:34:02 EDT 2014

On 03/31/2014 05:44 PM, William Clark wrote:
> Running the following from CentOS upstream:
> krb5-server-1.10.3-10.el6_4.6.x86_64
> 
> I am not adverse to going with the latest stable MIT version if it will
> help in this.

I think testing 1.12.1 would be worthwhile.  I don't know of any
specific bugs in 1.10 which could lead to a SIGABRT, but there are
numerous iprop and locking improvements which went into 1.11 and 1.12
but were too invasive to backport to 1.10.