> After running beagle-build-index on the "heavy" data set for a while, the
> number of open files kept growing; I killed the process at 257 open files,
..
> broken) the number of open files was at ~266. It's mostly .chm files, so
> maybe there's something broken? The ("small") index is fine, btw.
Hi dBera,
--On Monday, February 16, 2009 07:24:28 AM -0500 D Bera
wrote:
Nothing I can remember that would cause this. Could you use lsof to
figure out what kind of files are left opened for a long time ? lsof
should show about 10/20 indexable/data files that are opened at any
time and they
Hi Jens,
> after upgrading beagle from 0.3.5 to 0.3.8 (both Ubuntu packages), I
...
> same file with the error "process too big". When I use --disable-restart, it
> fails with "too many files open", which I can probably fix, but I was
> wondering what might have changed from 0.3.5 to 0.3.8 to caus
Hi everyone,
after upgrading beagle from 0.3.5 to 0.3.8 (both Ubuntu packages), I
encountered memory problems when using beagle-build-index in a
directory tree with _lots_ of files. In 0.3.5 it took some hours, but
worked in the end; in 0.3.8 it loops over and over and over, always
quitting a
