You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@lucene.apache.org by Marvin Humphrey <ma...@rectangular.com> on 2005/11/22 04:13:01 UTC
Lock Dir Location
Greets,
As I work on the ports for FSDirectory and FSLock, I'm wondering why
the file system directory itself shouldn't be used to hold the
lockfiles. If there's a write permissions problem, such as an
FSDirectory on CDrom, disableLocks takes care of it. Is there some
scenario having to do with mirroring that I haven't quite envisioned
yet, or something else?
Marvin Humphrey
Rectangular Research
http://www.rectangular.com/
---------------------------------------------------------------------
To unsubscribe, e-mail: java-dev-unsubscribe@lucene.apache.org
For additional commands, e-mail: java-dev-help@lucene.apache.org
Re: Lock Dir Location
Posted by Doug Cutting <cu...@apache.org>.
Marvin Humphrey wrote:
> As I work on the ports for FSDirectory and FSLock, I'm wondering why
> the file system directory itself shouldn't be used to hold the
> lockfiles. If there's a write permissions problem, such as an
> FSDirectory on CDrom, disableLocks takes care of it. Is there some
> scenario having to do with mirroring that I haven't quite envisioned
> yet, or something else?
On a multi-user system this permits the owner & maintainer of an index
to give read-only access to other users. Thus, for example, an
operating system might maintain an index of installed manual pages that
any user can search.
Doug
---------------------------------------------------------------------
To unsubscribe, e-mail: java-dev-unsubscribe@lucene.apache.org
For additional commands, e-mail: java-dev-help@lucene.apache.org