Re: [leafnode-list] lockfiles revisited

[Joerg Dietrich <joerg@xxxxxxxxxxxx>]

On Fri, Feb 16, 2001 at 01:35:21AM +0100, Matthias Andree wrote:
> > 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,

*If* we find out that overviews need to be locked and *if* we
want to do this fine grained it might help. I don't see how this
affects the caching of overview information.

Regards,
        Jo:rg

-- 
Fortune cookie of the day:
Math is like love -- a simple idea but it can get complicated.
		-- R. Drabek

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