Hi,
On Fri, 2006-06-16 at 10:21 -1000, Alec Burney wrote:
beagle seems not not remove its locks on the next startup after a very
unclean shutdown, meaning that once it tries to gain a lock and fails
because of the existing lock, it will stop indexing alltogether for that
session. then it will
Hi,
I just came across a project called beagle++ that seems to be going in
the direction i am aiming at with my SoC project.
http://beagle.kbs.uni-hannover.de/index.html
I just wonder why i never heard about it before. Has there been any
communication between the beagle++ guys and people on
beagle seems not not remove its locks on the next startup after a very
unclean shutdown, meaning that once it tries to gain a lock and fails
because of the existing lock, it will stop indexing alltogether for that
session. then it will not shutdown cleanly or remove the existing lock,
meaning
Hi,
I saw a link to this wiki on irc yesterday.
https://wiki.ubuntu.com/IntegratedDesktopSearch
Might be of interest. Competition leads to a healthy environment :)
- dBera
--
-
Debajyoti Bera @ http://dbera.blogspot.com
beagle / KDE fan
Hi,
I'm happy to announce the release of Beagle 0.2.7.
This version fixes the dreaded Lock obtain timed out bug, includes
a new SVG and marks the return of the CHM filter. It introduces a
compressed text cache, so that the disk space needed to generate
snippets is greatly reduced, and many more
Hi,
On Mon, 2006-06-19 at 14:23 +0200, Max wrote:
I just wonder why i never heard about it before. Has there been any
communication between the beagle++ guys and people on this list?
I also exchanged some private email with them a while back, but nothing
really came out of it.
Looks like
On Mon, 2006-06-19 at 08:19 -0700, Debajyoti Bera wrote:
beagle seems not not remove its locks on the next startup after a very
unclean shutdown, meaning that once it tries to gain a lock and fails
because of the existing lock, it will stop indexing alltogether for that
session. then it
