Strange behavior with kadmind and incremental propagation in 1.8.3

[vs_krb]

NIco

Looking at the release log for 1.8.6 from http://web.mit.edu/kerberos/krb5-1.8/krb5-1.8.6.html , I see the issue mentioned in this thread is addressed with that realease. I am wondering if you would still recommend folks on 1.8.6 to upgrade as well. 

We are running 1.8.6 and we are planning to turn on incremental propagation. Seeing the MIT documentation and forums, I get the impression that iprop is not as stable as a straight kprop push from master to slaves(I understand it is more complicated than a simple dump of db and shooting it across). But looking at this thread, the question that I get is whether we need to go 1.11 or at least 1.10 before turning on iprop.

Thanks
VS.

On Tuesday, February 12, 2013 4:11:43 PM UTC-5, Nico Williams wrote:
> Re-reading more closely it seems that krb5_put_principal() failed
> 
> because of the locking issue but nonetheless still created the iprop
> 
> ulog entry and marked it as committed.  That would be a nasty bug I
> 
> was not aware, but I believe it's fixed in master, and likely fixed in
> 
> 1.11.
> 
> 
> 
> Nico
> 
> --