x27;t think it is started by an apache daemon.
Will check it. Thanks
Kristian
> -Original Message-
> From: Morus Walter [mailto:[EMAIL PROTECTED]
> Sent: 13. april 2005 08:38
> To: java-user@lucene.apache.org; [EMAIL PROTECTED]
> Subject: RE: Lucene on Linux problem...
http://www.yawah.com
> -Original Message-
> From: Miles Barr [mailto:[EMAIL PROTECTED]
> Sent: 4. april 2005 10:25
> To: Lucene User
> Subject: Re: Lucene on Linux problem...
>
> On Sat, 2005-04-02 at 10:29 +0200, Kristian Ottosen wrote:
> > I wonder if there is
Kristian Ottosen writes:
>
> It seems to work now - but I would still love to see a good explanation.
>
How was your java application started? (sorry I you already explained,
I didn't keep the thread and the mailing list archive seems to be out
of order)
I remember strange problems (with mkdir
Original Message-
> From: Miles Barr [mailto:[EMAIL PROTECTED]
> Sent: 4. april 2005 10:25
> To: Lucene User
> Subject: Re: Lucene on Linux problem...
>
> On Sat, 2005-04-02 at 10:29 +0200, Kristian Ottosen wrote:
> > I wonder if there is general problem running Lucene o
On Sat, 2005-04-02 at 10:29 +0200, Kristian Ottosen wrote:
> I wonder if there is general problem running Lucene on top of some of the
> journaling file systems like ReiserFS or Ext3?
I haven't had any problems running Lucene on either of those file
systems. I've done updates to the index while pe
I've also been getting this error very rarely on a production system
with lots of search queries. The system is Fedora 1 using ext3. It
happens in the call to IndexReader.getCurrentVersion(indexPath). I
think it happens when the separate indexing process is running or has
just run (from a separa
On Saturday 02 April 2005 10:29, Kristian Ottosen wrote:
> Hello,
>
> I have really been pulling out hair for a while over this. The problem only
> occur using FSDirectory on some Linux system (some Debian, Suse and Redhat -
> but not all) and never under Windows, Solaris or Mac OS X.
>
> What h
