-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Hi,

> Nevermind, I was looking at the wrong function, and I see what's
> wrong. The short description is that we acquire a non-blocking lock
> when creating a DB, when we should be acquiring a blocking lock.  I
> have filed a pull request for the one-line fix: 
> https://github.com/krb5/krb5/pull/411

Yesterday I rebuilt our krb5 packages with your small patch and have
not received any more error messages. Perfect!

Thanks a lot,

Christopher

- -- 
======================================================
    Dipl.-Ing. Christopher Odenbach
    Zentrum fuer Informations- und Medientechnologien
    Universitaet Paderborn
    Raum N5.311
    odenb...@uni-paderborn.de
    Tel.: +49 5251 60 5315
======================================================
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2

iD8DBQFWzvCghxiCJKeLY0IRAidMAKCQdBE1ZYLbLB2isxRZK+A/UZrfSQCeIp/Q
dFgrNbufuQYn+ccCvYqrS6I=
=huKV
-----END PGP SIGNATURE-----
________________________________________________
Kerberos mailing list           Kerberos@mit.edu
https://mailman.mit.edu/mailman/listinfo/kerberos

Reply via email to