: 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: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
