Mailing-List: contact java-dev-help@lucene.apache.org; run by ezmlm
Precedence: bulk
Reply-To: java-dev@lucene.apache.org
Received-SPF: error (idunn.apache.osuosl.org: domain yahoo.co.uk from
 217.12.10.201 cause and error)
DomainKey-Status: good
DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws;
  s=s1024; d=yahoo.co.uk;
  h=Message-ID:Received:Date:From:Reply-To:Subject:To:In-Reply-To:MIME-Version:Content-Type;
  b=qY2HRmVQnfxgMMCzOWjSkdHYmM+wjY9H/oz+LpOciYMQd+7/i3xUi6esILI3qsVEuZnNuynxY1C87EY2WuYCxs/TRdAMX+ywF9crAASdKwLqx55CHEve+h5qdXGecN0IPFrDiXZ4V8VxE6/aQhBA8KyaqtlDRzF7R2K27S0lWV4=
  ;
Message-ID: <20060913200942.16169.qmail@web25903.mail.ukl.yahoo.com>
Date: Wed, 13 Sep 2006 20:09:42 +0000 (GMT)
From: eks dev <eksdev@yahoo.co.uk>
Reply-To: eks dev <eksdev@yahoo.co.uk>
Subject: Re: [jira] Commented: (LUCENE-665) temporary file access denied on
 Windows
To: java-dev@lucene.apache.org
In-Reply-To: <Pine.LNX.4.58.0609131257410.21953@hal.rescomp.berkeley.edu>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii

not promoting, "let lucene fix all Winblows problems", just saying, if someone has cool, simple trick in patch form, that hurts nobody, would be nice to accept it. Enough people burned their fingers on this one

----- Original Message ----
From: Chris Hostetter <hossman_lucene@fucit.org>
To: java-dev@lucene.apache.org
Sent: Wednesday, 13 September, 2006 10:04:05 PM
Subject: RE: [jira] Commented: (LUCENE-665) temporary file access denied on Windows

: While what you say is true about indexing should be disabled, that
: really doesn't solve the actual issue. Administrators of applications
: using lucene often do not have control over the actual machine and thus
: cannot determine what is and is not installed. Besides that, many of us

no, but they can st the operating params of the software they support --
as far as i can tell based on what i've read about the issue, the problem
stems from software that does what seems to be the equivilent of trying to
open any file that has recently been closed by any other app ... as
a java library Lucene shouldn't be expected to guard against that any more
then it should be expected to guard against the possibility of people
randmoly renaming or deleting files in the index directory -- Lucene makes
some files, and it expects to manage them without interference from
anything else -- as long as that expectation is documented (and i'll
admit, those expectations could be documented more thoroughly) then i
think our work here is done.

Dealing withthis problem becomes the topic of a FAQ about the cause with a
pointer to a Wiki explaining the details and (*hopefully*) a list of crazy
registry hacks you can use to disable it on a per directory basis.

(DISCLAIMER: I am not saying such hacks exist, merely that i hope some
method of disabling this "feature" exists and if it does pointeres on how
to do so would be useful)


-Hoss


---------------------------------------------------------------------
To unsubscribe, e-mail: java-dev-unsubscribe@lucene.apache.org
For additional commands, e-mail: java-dev-help@lucene.apache.org


---------------------------------------------------------------------
To unsubscribe, e-mail: java-dev-unsubscribe@lucene.apache.org
For additional commands, e-mail: java-dev-help@lucene.apache.org