I have been having a hard time getting beagle to run through the
night. After some debugging, I think here's why:
DEBUG: No activity for 30.0 minutes, shutting down
DEBUG: (1) Waiting for 1 worker...
DEBUG: waiting for server '/home/kbreit/.beagle/socket-helper'
DEBUG: Server '/home/kbreit/.beagl
On Thu, 2005-10-13 at 11:06 +0200, Albert Vilella wrote:
> Hi all,
>
> Is there any compromising situation that would break beagled from doing
> a:
>
> beagled --fg
> # after some minutes/hours
> Ctrl-z
> # after some minutes/hours
> fg
This would cause the daemon to suspend, but not the index h
Hi,
On Wed, 2005-10-12 at 13:23 -0400, Andrew Conkling wrote:
> I just had a general question: is it possible to prevent errors like
> this happening? It doesn't seem ideal to require Mozilla/FF to use
> best, or to be restricted to using a certain version or hand-editing
> /usr/bin/best (and may
Hi all,
Is there any compromising situation that would break beagled from doing
a:
beagled --fg
# after some minutes/hours
Ctrl-z
# after some minutes/hours
fg
I got this error when doing so:
DEBUG: worker added: name=HandleConnection (12) refcount=1
DEBUG: worker added: name=HandleConnection (
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
D Bera writes:
> Are you indexing files on NFS (or something mounted remotely) ? This
> seems to be a problem with index synchronization (which, I think,
> copies the index locally, does more indexing and copies it back upon
> shutdown). I noticed the
