On Mon, 21 Mar 2005 22:36:18 -0500, Lukin <[EMAIL PROTECTED]> wrote:
> FWIW - libgmime doesn't seem to be considered 'stable' for the hoary
> version of ubuntu. For some reason libgmime-cil installed without
> problem, but I couldn't find libgmime via the update manager.
>
certainly on all my hoa
FWIW - libgmime doesn't seem to be considered 'stable' for the hoary
version of ubuntu. For some reason libgmime-cil installed without
problem, but I couldn't find libgmime via the update manager.
I cant remember where I found it, but I installed it from here
http://mirror.clarkson.edu/pub/distrib
Hi,
On Mon, 2005-03-21 at 15:51 +, Daniel Drake wrote:
> Shane Bishop wrote:
> > It still has the problem with generating huge amounts of logs.
>
> Same exception message? If so, would I be right in saying that you are an
> Ubuntu user, and don't have libgmime installed (but do have libgmime
Shane Bishop wrote:
It still has the problem with generating huge amounts of logs.
Same exception message? If so, would I be right in saying that you are an
Ubuntu user, and don't have libgmime installed (but do have libgmime-sharp)?
___
Dashboard-hacker
I've updated my kernel version to 2.6.11
(gentoo-dev-sources-2.6.11) and this solve the
problem!
Thanks!
Sergio.
--- Jon Trowbridge <[EMAIL PROTECTED]> wrote:
> On Tue, 2005-03-15 at 13:04 +0100, Sergio Espeja
> wrote:
> > when I start it up (beagled) it takes all the
> memory disponible.
> > Thi
I did get it to compile on Tuesday, and then sometime later in the week.
It still has the problem with generating huge amounts of logs.
Shane
Daniel Drake wrote:
Hi Shane,
Shane Bishop wrote:
It's actually CVS from last Thursday or Friday. I wasn't able to get
cvs to compile at all yesterday. I'
Hi Shane,
Shane Bishop wrote:
It's actually CVS from last Thursday or Friday. I wasn't able to get cvs to
compile at all yesterday. I'll try again today though.
Any progress on this? If you have compilation troubles, please post the
compile error.
Daniel
_
It's actually CVS from last Thursday or Friday. I wasn't able to get
cvs to compile at all yesterday. I'll try again today though.
Shane
Joe Shaw wrote:
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.
On Tue, 2005-03-15 at 13:04 +0100, Sergio Espeja wrote:
> 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 have an inotify kernel? Beagle requires inotify 0.18. Huge
memory usage at start-up can be ca
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
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: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
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.
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
