Hi,
On Tue, 2005-09-20 at 10:08 +0100, Darren Davison wrote:
> It's the IMLog backend.
Thanks a lot for tracking this down, I just checked in a fix for it into
CVS. It is related to the fact that you're running without inotify. If
you are building from source you can add the line:
task
On Mon, 2005-09-19 at 17:24 -0400, Joe Shaw wrote:
> Someone else was seeing this too. The most helpful thing would be if
> you could track this down to a specific backend, by using
> --allow-backend as an argument to beagled. I'd suggest blowing away
> ~/.beagle each time so that you recreate a
Hi,
On Mon, 2005-09-19 at 22:14 +0100, Darren Davison wrote:
> Hi guys, congrats on the 0.1.0 release!
Thanks!
> Now, I'm not yet running a 2.6.13 kernel, so have the wrong inotify version,
> but I'm not sure that's at fault here. My understanding is that inotify won't
> affect the indexer much
Hi guys, congrats on the 0.1.0 release!
I upgraded beagle from 0.0.12 to 0.1.0 and all the various dependencies (I
think I got them all at any rate) and blew away ~/.beagle before starting the
new version just in case.
Now, I'm not yet running a 2.6.13 kernel, so have the wrong inotify version,
