Ticket File Cached in Memory?

[John W. M. Stevens]

Hi,

I'm developing an authenticated peer-to-peer, messaging service that uses
Kerberos 5.

So far, so good, thanks to a few pithy pointers from this list.  I've
gotten far enough along to be doing performance testing, and the system
is thrashing on opening, reading and closing the file used to store
tickets.

The obvious solution would be to have the tickets cached in memory, but
I can't find any suggestions on how to do that, or even if it is possible.

And, too, I've got a file handle leak (on the ticket file) somewhere, but
that won't matter if I can't speed things up a bit.  And if I speed it up
by caching, that bug won't really matter any more.

Any hints or pointers to what I should be reading to help me figure
how/if memory vs. file caching is possible?

Thanks!
John S.
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 197 bytes
Desc: Digital signature
Url : http://mailman.mit.edu/pipermail/krbdev/attachments/20090825/90309c63/attachment.bin