Re: documentation vs specification
Harry Coin <[email protected]>
| Newsgroups | gmane.comp.encryption.kerberos.heimdal.general |
|---|---|
| Message-ID | <[email protected]> |
On 10/3/2011 3:12 PM, [email protected] wrote: > "recommended ccache update and view-refresh sequence" How about just doubling the file size? Updaters change so if the file isn't empty, it writes the whole new business at the end of the current file, commits the changes (close/reopen?). Only then writes them again at the beginning overwriting what's there. If the file is empty it just writes it all twice. Readers automatically try the second half if there are problems with the first without trying to puzzle through why the first didn't work. Avoids the whole (re)create/truncate/delete/rename/ownership/permission/locking/exclusivity follies. Also guarantees that at no moment during the process will reading perfectly valid credentials fail, or need be delayed beyond the price of a second try. Harry