On Tue, 2005-03-15 at 13:23 -0600, Shane Bishop wrote:
> Here's what is getting repeated on the 10 GB log file:
>
> 05-03-15 10.05.10.47 20199 Beagle WARN: Caught exception in DoTaskReal
> 05-03-15 10.05.10.47 20199 Beagle WARN:
> Tag: /home/sbishop/.evolution/mail/local/Inbox
> 05-03-15 10.05.10.
I've opened a bug on this issue.
http://bugzilla.gnome.org/show_bug.cgi?id=170513
Shane: you might want to add yourself to the cc: list.
Thanks,
-J
___
Dashboard-hackers mailing list
Dashboard-hackers@gnome.org
http://mail.gnome.org/mailman/listinfo/d
-- Forwarded message --
From: Nils Erik Svangård <[EMAIL PROTECTED]>
Date: Wed, 16 Mar 2005 01:07:00 +0100
Subject: Re: Debian Install howto2
To: mm <[EMAIL PROTECTED]>
Hi!
On debian i get this when running beagled -fg -debug
** (beagled:23452): WARNING **: Could not load class f
On Tue, 2005-03-15 at 15:03 -0500, Robert Love wrote:
> Say you have an automount at /foo/bar. Then (in Util in the beagle src)
>
> ./inotify-test -r /foo/bar
>
> and let me know what happens.
Oh, we'd want the mount to not yet be mounted, obviously.
Robert Love
__
My minions,
Do any of you use autofs?
If so, I need you! Andrew Morton is interested in what happens if an
inotify watch triggers an automount.
Finding out should be easy.
Say you have an automount at /foo/bar. Then (in Util in the beagle src)
./inotify-test -r /foo/bar
and let me k
Here's what is getting repeated on the 10 GB log file:
05-03-15 10.05.10.47 20199 Beagle WARN: Caught exception in DoTaskReal
05-03-15 10.05.10.47 20199 Beagle WARN: Tag:
/home/sbishop/.evolution/mail/local/Inbox
05-03-15 10.05.10.47 20199 Beagle WARN: Creator:
05-03-15 10.05.10.47
Hi,
On Tue, 2005-03-15 at 10:10 -0600, Shane Bishop wrote:
> Here it is:
> 10823940/home/name/.beagle/Log
Ok. See what Jon said in another mail in this thread. Presumably the
index helper is getting stuck.
Joe
___
Dashboard-hackers mailing l
Dnia 15-03-2005, wto o godzinie 11:11 -0500, Ken VanDine napisał(a):
> I had not noticed this, but this thread made me look. I have a single
> IndexHelper log file that is 8.1G. All the others look reasonable.
> Also, it isn't the latest file.
>
> A little info:
> mono 1.1.4
> beagle 0.0.7
> db
On Tue, 2005-03-15 at 11:36 -0600, Jon Trowbridge wrote:
> On Tue, 2005-03-15 at 17:32 +0100, Albert Vilella wrote:
> > export _BEAGLED_INDEX_HELPER_PATH=/usb/lib/beagle/
>
> This should get set automatically in the beagled script. What do you
> see when you grep for _BEAGLED_INDEX_HELPER_PATH on
On Tue, 2005-03-15 at 17:32 +0100, Albert Vilella wrote:
> export _BEAGLED_INDEX_HELPER_PATH=/usb/lib/beagle/
This should get set automatically in the beagled script. What do you
see when you grep for _BEAGLED_INDEX_HELPER_PATH on beagled?
Thanks,
-J
___
On Tue, 2005-03-15 at 11:11 -0500, Ken VanDine wrote:
> I had not noticed this, but this thread made me look. I have a single
> IndexHelper log file that is 8.1G.
Presumably the IndexHelper got stuck in some sort of fast loop, maybe
throwing an exception that is caught and logged every time? Cou
Sorry, when I say that beagle consumes lots of memory
I'm referring to system memory, but I didn't take
notice about storage... I'll see it and write another
mail with results. But the problem is that consumes
all the system memory and a great part of swap! And
I've 1Gb of RAM an 2Gb of swap!
Any
Based on Matthew fc3 rpms,
It won't start beagled or best without defining:
cd /usr/local/lib/beagle
sudo ln -s /usr/local/lib/mono/dbus-sharp/dbus-sharp.dll .
and
export _BEAGLED_INDEX_HELPER_PATH=/usb/lib/beagle/
Bests,
Albert.
___
Dashboard-
Apparently, it won't start beagled without defining:
export _BEAGLED_INDEX_HELPER_PATH=/usb/lib/beagle/
Bests,
Albert.
___
Dashboard-hackers mailing list
Dashboard-hackers@gnome.org
http://mail.gnome.org/mailman/listinfo/dashboard-hackers
I had not noticed this, but this thread made me look. I have a single
IndexHelper log file that is 8.1G. All the others look reasonable.
Also, it isn't the latest file.
A little info:
mono 1.1.4
beagle 0.0.7
dbus 0.23.3
--Ken
On Tue, 2005-03-15 at 11:02 -0500, Joe Shaw wrote:
> Hi,
>
> On T
Here it is:
10823940 /home/name/.beagle/Log
4052 /home/name/.beagle/FileSystemIndex
176 /home/name/.beagle/BlamIndex
24 /home/name/.beagle/LifereaIndex
24 /home/name/.beagle/MailIndex
636 /home/name/.beagle/WebHistoryIndex
40 /home/name/.beagle/TomboyIndex
2712
Hi,
On Tue, 2005-03-15 at 08:39 -0600, Shane Bishop wrote:
> I'm not sure what you are referring to (system memory, or actual
> storage), but I ran into a similar problem the other day. The beagle
> logs took over my hard drive (all 74 GB), and I could no longer log into
> gnome, it was crazy.
> Now, if you have sometime please head over to the install page and
> check out the information for your particular distribution. Please
> make sure stuff didn't get chopped off or left out. Thanks
>
> http://beaglewiki.org/index.php/Installing%20Beagle
For Fedora Core, there is a dependency m
I'm not sure what you are referring to (system memory, or actual
storage), but I ran into a similar problem the other day. The beagle
logs took over my hard drive (all 74 GB), and I could no longer log into
gnome, it was crazy. Is there a way to limit this? It took about a week
or so from when
Hello!
I've been trying beagle and I notice that when I start
it up (beagled) it takes all the memory disponible.
This makes my system unusable.
I use beagle 0.0.7 and mono 1.1.4.
Do you know how to limit the amount of memory beagle
is going to use? or another solution?
Thanks!
Sergio.
20 matches
Mail list logo