[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [leafnode-list] lockfiles revisited

On 16 Feb 2001, Matthias Andree wrote:
> Joerg Dietrich <joerg@xxxxxxxxxxxx> writes:
> > Overviews are not locked. It is probably silently assumed that if
> > two processes mess an .overview file up, the next call to
> > getxover() will repair it. Maybe one should consider writing an
> > fcntl() wrapper that takes abritrary filenames as arguments and
> > locks or releases these files. Once my exams are over...
> What will that help? It will totally spoil performance, since if you're
> doing it seriously, you need to obtain the exclusive lock before reading
> the overview, you cannot cache it. Record locking might be a way out,
> but I'm not sure how portable THAT is, and it would require somewhat
> fixed-length records. OTOH, one might try SleepCat DB (a concurrent
> write access version), however, I'm not sure how stable these are and if
> license conditions would suit leafnode's needs.

SleepyCat uses GPL whereas Leafnode is currently BSD licensed. This isn't
a problem for me, though it might be for some people.

***** Phil Hunt ***** 
"An unforseen issue has arisen with your computer. Don't worry your silly 
little head about what has gone wrong; here's a pretty animation of a 
paperclip to look at instead."
         -- Windows2007 error message

leafnode-list@xxxxxxxxxxxxxxxxxxxxxxxxxxxx -- mailing list for leafnode
To unsubscribe, send mail with "unsubscribe" in the subject to the list