[1280] in Kerberos_V5_Development
Re: changing libkdb database open/lock semantics
daemon@ATHENA.MIT.EDU (Mark Eichin)
Mon Jun 3 16:35:09 1996
To: "Barry Jaspan" <bjaspan@MIT.EDU>
Cc: krbdev@MIT.EDU
From: Mark Eichin <eichin@MIT.EDU>
Date: 03 Jun 1996 16:34:07 -0400
In-Reply-To: "Barry Jaspan"'s message of Mon, 3 Jun 96 14:33:10 -0400
>> This scheme does have the disadvantage that the KDC opens and closes
>> the database for every transaction which is clearly ineffecient, but
Hmm. If we switch to doing this anyway, maybe gdbm will work (it does
it's own filelocking -- which conflicts with the krb5 mechanism.) I
wonder if that's going to make it *too* expensive, but I don't have
any data on the subject...
