Re: iprop: Problem forcing complete database sync
Nico Williams <[email protected]> Mon, 09 Oct 2017 19:47:29 +0000
| Newsgroups | gmane.comp.encryption.kerberos.heimdal.general |
|---|---|
| Message-ID | <CAK3OfOjavpPWd1upjtQQ9VdZAP8wkO8MJWBMaUpwz+bSqZpF-w@mail.gmail.com> |
On Mon, Oct 9, 2017 at 3:40 PM Nico Williams <[email protected]> wrote: > On Mon, Oct 9, 2017 at 3:19 AM Harald Barth <[email protected]> wrote: > >> >> Have I got this right? >> >> 1. Does write_dump(context, s, database, current_version) always write >> a comptele dump no matter the value of current_version? > > > Yes. BTW, there's a bug here in that we don't remove the dump on failure > or rename it into place on success. This means that a failure in the > middle of dumping may leave a valid-looking but incomplete dump that may > then be sent to slaves. > Actually, i tell a lie. This is only a problem on version zero. >