[krbdev.mit.edu #7695] krb5-1.11.3/1.10.6 - full resync may fail and still result in ulog being updated

[Richard Basch via RT]

It might be related but I prefer defensive checks and at best it is currently a very spotty check which might be a problem if you run multiple realms on a box. I can think of a few conditions without hierarchical but most would be multiple processes and an inadvertent configuration error.


Richard Basch

(Sent via my Samsung GALAXY Sâ„¢4)

-------- Original message --------
From: Greg Hudson via RT <rt-comment at krbdev.mit.edu> 
Date: 08/29/2013  07:28  (GMT-05:00) 
To: basch at alum.mit.edu 
Subject: [krbdev.mit.edu #7695] krb5-1.11.3/1.10.6 - full resync may fail and still result in ulog being updated 
 
In the absence of hierarchical iprop, I can't come up with a scenario 
where current_dump_sno_in_ulog() erroneously returns true.  Can you 
outline a series of operations on the master which would cause it to do 
so?