Re: beagle-0.1.1 and /tmp
Hi Jon It's done: Bug 322106: beagle-0.1.2 fills /tmp partition Rgds, -- Joris To make sure that this issue doesn't fall through the cracks, could you please file a bug report at bugzilla.gnome.org? Thanks, -J This message was sent using IMP, the Internet Messaging Program. ___ Dashboard-hackers mailing list Dashboard-hackers@gnome.org http://mail.gnome.org/mailman/listinfo/dashboard-hackers
Re: beagle-0.1.1 and /tmp
To make sure that this issue doesn't fall through the cracks, could you please file a bug report at bugzilla.gnome.org? Thanks, -J On Sun, 2005-11-20 at 22:08 +0100, Joris Vuffray wrote: > Yes, I confirm > > The files are created when I start beagle, and are of diff. types, mails, > html, docs, etc... ___ Dashboard-hackers mailing list Dashboard-hackers@gnome.org http://mail.gnome.org/mailman/listinfo/dashboard-hackers
Re: beagle-0.1.1 and /tmp
Yes, I confirm The files are created when I start beagle, and are of diff. types, mails, html, docs, etc... I'm running beagle-0.1.2 on gentoo: $ beagled --list-backends Current available backends: User: - Mail - KMail - Files - GaimLog - IndexingService - Tomboy - Blam - Liferea - Akregator - Kopete - Google Rgds, --- Joris > > On Sat, 2005-11-19 at 22:47 -0500, D Bera wrote: > > AFAIK this problem was fixed a few release back and tmp file behaviour > > should be ok in 0.1.1+. Can you confirm that the files in /tmp are > > created by beagle ? -- Joris Vuffray <[EMAIL PROTECTED]> signature.asc Description: This is a digitally signed message part ___ Dashboard-hackers mailing list Dashboard-hackers@gnome.org http://mail.gnome.org/mailman/listinfo/dashboard-hackers
Re: beagle-0.1.1 and /tmp
AFAIK this problem was fixed a few release back and tmp file behaviour should be ok in 0.1.1+. Can you confirm that the files in /tmp are created by beagle ? On 11/19/05, Joris Vuffray <[EMAIL PROTECTED]> wrote: > Hi, > I'm still experiencing the same problem with 0.1.2 > Any idea? > > Rgds, > -- Joris > > On Thu, 2005-10-06 at 22:00 +0200, Joris Vuffray wrote: > > Hi > > I have a problem with the beagle daemon which fill my /tmp filesystem > > with tmp* Files. I'm using aa tmpfs virtual filesystem on my laptop and > > the available space on this is limited. > > Is there a possibility to configure the beagle daemon to use another > > directory to store its temp files? > > > Joris Vuffray <[EMAIL PROTECTED]> > > > -BEGIN PGP SIGNATURE- > Version: GnuPG v1.4.1 (GNU/Linux) > > iD8DBQBDf05m1ycndYO88hcRAmUkAJsES6PjOIT+eSQn4M+kAa7Xsl7K4wCeMC1B > cKOGedJSehzutx4Uf3K+N7U= > =X5ia > -END PGP SIGNATURE- > > > ___ > Dashboard-hackers mailing list > Dashboard-hackers@gnome.org > http://mail.gnome.org/mailman/listinfo/dashboard-hackers > > > ___ Dashboard-hackers mailing list Dashboard-hackers@gnome.org http://mail.gnome.org/mailman/listinfo/dashboard-hackers
Re: beagle-0.1.1 and /tmp
Hi, I'm still experiencing the same problem with 0.1.2 Any idea? Rgds, -- Joris On Thu, 2005-10-06 at 22:00 +0200, Joris Vuffray wrote: > Hi > I have a problem with the beagle daemon which fill my /tmp filesystem > with tmp* Files. I'm using aa tmpfs virtual filesystem on my laptop and > the available space on this is limited. > Is there a possibility to configure the beagle daemon to use another > directory to store its temp files? Joris Vuffray <[EMAIL PROTECTED]> signature.asc Description: This is a digitally signed message part ___ Dashboard-hackers mailing list Dashboard-hackers@gnome.org http://mail.gnome.org/mailman/listinfo/dashboard-hackers
Re: Beagle 0.1.1
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Darren Davison writes: > On Tue, Oct 04, 2005 at 11:21:22PM +0100, Henry S. Thompson wrote: >> Jon Trowbridge writes: >> >> > On Tue, 2005-10-04 at 19:11 +0100, Henry S. Thompson wrote: >> >> Unhandled Exception: System.ArgumentNullException: null key >> > >> > That is fixed in 0.1.1. >> >> I'm using 0.1.1 :-( > > I think I was the one who reported the issue in 0.1.0 - certainly looks > similar - it was in the IMLog backend. > > I still get the exception too in 0.1.1 although it doesn't seem to stop beagle > working now whereas it did in 0.1.0 > > Might try and track it down a bit further later.. So the null key crash I'm getting does stop all indexing work, but I've patched around it and things seem OK now (although I understand almost nothing about the code I patched, so who knows) -- see bugzilla 317997 [1]. ht [1] http://bugzilla.gnome.org/show_bug.cgi?id=317997 - -- Henry S. Thompson, HCRC Language Technology Group, University of Edinburgh Half-time member of W3C Team 2 Buccleuch Place, Edinburgh EH8 9LW, SCOTLAND -- (44) 131 650-4440 Fax: (44) 131 650-4587, e-mail: [EMAIL PROTECTED] URL: http://www.ltg.ed.ac.uk/~ht/ [mail really from me _always_ has this .sig -- mail without it is forged spam] -BEGIN PGP SIGNATURE- Version: GnuPG v1.2.6 (GNU/Linux) iD8DBQFDRN4tkjnJixAXWBoRAmR/AJ9UQSKOGUdHtbyISt9fafpuNkYaIwCdGOch z+Qw1VSNq4tLjRhJW/iNBqU= =C+kd -END PGP SIGNATURE- ___ Dashboard-hackers mailing list Dashboard-hackers@gnome.org http://mail.gnome.org/mailman/listinfo/dashboard-hackers
Re: Beagle 0.1.1
On Tue, Oct 04, 2005 at 11:21:22PM +0100, Henry S. Thompson wrote: > Jon Trowbridge writes: > > > On Tue, 2005-10-04 at 19:11 +0100, Henry S. Thompson wrote: > >> Unhandled Exception: System.ArgumentNullException: null key > > > > That is fixed in 0.1.1. > > I'm using 0.1.1 :-( I think I was the one who reported the issue in 0.1.0 - certainly looks similar - it was in the IMLog backend. I still get the exception too in 0.1.1 although it doesn't seem to stop beagle working now whereas it did in 0.1.0 Might try and track it down a bit further later.. -- Darren Davison Public Key: 0xDD356B0D ___ Dashboard-hackers mailing list Dashboard-hackers@gnome.org http://mail.gnome.org/mailman/listinfo/dashboard-hackers
Re: Beagle 0.1.1
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Jon Trowbridge writes: > On Tue, 2005-10-04 at 23:24 +0100, Henry S. Thompson wrote: >> Probably - I wasn't aware Beagle was vulnerable in this way -- where >> can I find out more about 'objectionable' files? > > Sometimes files that are corrupted or malformed can trigger bugs in the > filters, causing us to consume more memory and/or CPU than we'd like. > This can also happens with certain types of extremely large files, and > is usually a problem with the more complex file formats. For example, > indexing very large (i.e. 500 page) Word document tends to cause a nasty > spike in CPU usage, and very large HTML files (like auto-generated > tables with thousands of rows) require a lot of memory to index. > > These sorts of things are generally related to not-easily-fixable issues > with third-party libraries that we use to process these file formats. > But even if they aren't easily fixable, we'd like to try. If you have a > document that causes these sorts of problems, please let us know. > Offending documents can be attached to bug reports at > bugzilla.gnome.org, or can be e-mailed directly to us if they contain > private/sensitive information. OK, that helps me understand, thanks. I'm going to continue sending reports about the state of my efforts to get this running, as I know from past experience that other newcomers welcome evidence that they are not alone. . . I'll file detailed bug reports via bugzilla. Two main areas of difficulty and one minor at the moment: 1) Not all directories are indexed: If I start with one root, I get repeated messages that that root is done, but nothing gets indexed. If I start with one of its subdirectories, _some_, but not all, of the sub-subdirectories then get scanned and indexed. Any idea what I can look at to help debug this? 2) Null key exception crashes the indexer, and although beagled is still running, it's no longer indexing. Details in Bugzilla. 3) The log fills up with INFO: NetBeagleConfigurationChanged EventHandler invoked INFO: WebServicesConfigurationChanged EventHandler invoked every minute. I suppose this may be because my .beagle directory is on NFS -- I'll try moving it. ht - -- Henry S. Thompson, HCRC Language Technology Group, University of Edinburgh Half-time member of W3C Team 2 Buccleuch Place, Edinburgh EH8 9LW, SCOTLAND -- (44) 131 650-4440 Fax: (44) 131 650-4587, e-mail: [EMAIL PROTECTED] URL: http://www.ltg.ed.ac.uk/~ht/ [mail really from me _always_ has this .sig -- mail without it is forged spam] -BEGIN PGP SIGNATURE- Version: GnuPG v1.2.6 (GNU/Linux) iD8DBQFDQ5lGkjnJixAXWBoRAkprAJ9M5Xo2JaUfl78tvi9JQygvNkoBUgCeMVzW Sa3VX2KhaEyMtxRjUvgz+i8= =yT+b -END PGP SIGNATURE- ___ Dashboard-hackers mailing list Dashboard-hackers@gnome.org http://mail.gnome.org/mailman/listinfo/dashboard-hackers
Re: Beagle 0.1.1
On Tue, 2005-10-04 at 23:24 +0100, Henry S. Thompson wrote: > Probably - I wasn't aware Beagle was vulnerable in this way -- where > can I find out more about 'objectionable' files? Sometimes files that are corrupted or malformed can trigger bugs in the filters, causing us to consume more memory and/or CPU than we'd like. This can also happens with certain types of extremely large files, and is usually a problem with the more complex file formats. For example, indexing very large (i.e. 500 page) Word document tends to cause a nasty spike in CPU usage, and very large HTML files (like auto-generated tables with thousands of rows) require a lot of memory to index. These sorts of things are generally related to not-easily-fixable issues with third-party libraries that we use to process these file formats. But even if they aren't easily fixable, we'd like to try. If you have a document that causes these sorts of problems, please let us know. Offending documents can be attached to bug reports at bugzilla.gnome.org, or can be e-mailed directly to us if they contain private/sensitive information. -J ___ Dashboard-hackers mailing list Dashboard-hackers@gnome.org http://mail.gnome.org/mailman/listinfo/dashboard-hackers
Re: Beagle 0.1.1
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 D Bera writes: >> Unhandled Exception: System.ArgumentNullException: null key >> Parameter name: key >> in [0x000c7] System.Collections.Hashtable:Find (System.Object key) >> in [0x2] (at >> /tmp/scratch/BUILD/mono-1.1.8.3/mcs/class/corlib/System.Collections/Hashtable.cs:395) >> System.Collections.Hashtable:Contains (System.Object key) >> in <0x00231> Beagle.Util.Scheduler:Worker () >> in (wrapper delegate-invoke) System.MulticastDelegate:invoke_void () >> >> Is this progress? > > 8-) Nops... its an error. > But I remember seeing some question (either in mailing list or irc) > about the exception above. I dont remember the problem or fix. Do you > have any objectionable files in the directory /disk/b ? Any ppt or doc > files ? Probably - I wasn't aware Beagle was vulnerable in this way -- where can I find out more about 'objectionable' files? Thanks, ht - -- Henry S. Thompson, HCRC Language Technology Group, University of Edinburgh Half-time member of W3C Team 2 Buccleuch Place, Edinburgh EH8 9LW, SCOTLAND -- (44) 131 650-4440 Fax: (44) 131 650-4587, e-mail: [EMAIL PROTECTED] URL: http://www.ltg.ed.ac.uk/~ht/ [mail really from me _always_ has this .sig -- mail without it is forged spam] -BEGIN PGP SIGNATURE- Version: GnuPG v1.2.6 (GNU/Linux) iD8DBQFDQwEskjnJixAXWBoRAs3iAJ90KMp/VtjdR38q3aJxLpXJfgxt3wCffrCI oKi4fF80sKEa44RKNR2HkMg= =mh/z -END PGP SIGNATURE- ___ Dashboard-hackers mailing list Dashboard-hackers@gnome.org http://mail.gnome.org/mailman/listinfo/dashboard-hackers
Re: Beagle 0.1.1
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Jon Trowbridge writes: > On Tue, 2005-10-04 at 19:11 +0100, Henry S. Thompson wrote: >> Unhandled Exception: System.ArgumentNullException: null key > > That is fixed in 0.1.1. I'm using 0.1.1 :-( ht - -- Henry S. Thompson, HCRC Language Technology Group, University of Edinburgh Half-time member of W3C Team 2 Buccleuch Place, Edinburgh EH8 9LW, SCOTLAND -- (44) 131 650-4440 Fax: (44) 131 650-4587, e-mail: [EMAIL PROTECTED] URL: http://www.ltg.ed.ac.uk/~ht/ [mail really from me _always_ has this .sig -- mail without it is forged spam] -BEGIN PGP SIGNATURE- Version: GnuPG v1.2.6 (GNU/Linux) iD8DBQFDQwBrkjnJixAXWBoRAoE7AJ9LZehkmVC1xBJaKXJMRZ4He0+ldgCfarSS /JApVex2W67kpKYnnnKXicM= =mbBJ -END PGP SIGNATURE- ___ Dashboard-hackers mailing list Dashboard-hackers@gnome.org http://mail.gnome.org/mailman/listinfo/dashboard-hackers
Re: Beagle 0.1.1
> >> That's not unreasonable, of course, but it's not recursing, and so is > >> looping very fast! That is, it's not actually indexing any files, > >> which are all in subdirectories. . . > > > > I also noticed similar behaviour - wait for some time - it takes a > > while for the file system backend to find the subdirectories and > > actually index the files in them. > > On second thought, probably the poll time for non-inotify case > > shouldnt be that low. > > So after about 1 hour, I got the following: > > ... > DEBUG: Done crawling '/disk/b' > DEBUG: Done crawling '/disk/b' > > Unhandled Exception: System.ArgumentNullException: null key > Parameter name: key > in [0x000c7] System.Collections.Hashtable:Find (System.Object key) > in [0x2] (at > /tmp/scratch/BUILD/mono-1.1.8.3/mcs/class/corlib/System.Collections/Hashtable.cs:395) > System.Collections.Hashtable:Contains (System.Object key) > in <0x00231> Beagle.Util.Scheduler:Worker () > in (wrapper delegate-invoke) System.MulticastDelegate:invoke_void () > > Is this progress? 8-) Nops... its an error. But I remember seeing some question (either in mailing list or irc) about the exception above. I dont remember the problem or fix. Do you have any objectionable files in the directory /disk/b ? Any ppt or doc files ? ___ Dashboard-hackers mailing list Dashboard-hackers@gnome.org http://mail.gnome.org/mailman/listinfo/dashboard-hackers
Re: Beagle 0.1.1
On Tue, 2005-10-04 at 19:11 +0100, Henry S. Thompson wrote: > Unhandled Exception: System.ArgumentNullException: null key That is fixed in 0.1.1. -J ___ Dashboard-hackers mailing list Dashboard-hackers@gnome.org http://mail.gnome.org/mailman/listinfo/dashboard-hackers
Re: Beagle 0.1.1
Hi, On Tue, 2005-10-04 at 15:36 +, Charlie Law wrote: > Has the Beagle wiki site been hijacked? I get a page about Banshee music file > sharing. The Beagle and Banshee wikis are hosted off the same machine. This might be vhost/caching issue on either the server or (since you mentioned later that you're using a VPN) your client. Try shift-clicking refresh. Joe ___ Dashboard-hackers mailing list Dashboard-hackers@gnome.org http://mail.gnome.org/mailman/listinfo/dashboard-hackers
Re: Beagle 0.1.1
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 D Bera writes: >> That's not unreasonable, of course, but it's not recursing, and so is >> looping very fast! That is, it's not actually indexing any files, >> which are all in subdirectories. . . > > I also noticed similar behaviour - wait for some time - it takes a > while for the file system backend to find the subdirectories and > actually index the files in them. > On second thought, probably the poll time for non-inotify case > shouldnt be that low. So after about 1 hour, I got the following: ... DEBUG: Done crawling '/disk/b' DEBUG: Done crawling '/disk/b' Unhandled Exception: System.ArgumentNullException: null key Parameter name: key in [0x000c7] System.Collections.Hashtable:Find (System.Object key) in [0x2] (at /tmp/scratch/BUILD/mono-1.1.8.3/mcs/class/corlib/System.Collections/Hashtable.cs:395) System.Collections.Hashtable:Contains (System.Object key) in <0x00231> Beagle.Util.Scheduler:Worker () in (wrapper delegate-invoke) System.MulticastDelegate:invoke_void () Is this progress? ht - -- Henry S. Thompson, HCRC Language Technology Group, University of Edinburgh Half-time member of W3C Team 2 Buccleuch Place, Edinburgh EH8 9LW, SCOTLAND -- (44) 131 650-4440 Fax: (44) 131 650-4587, e-mail: [EMAIL PROTECTED] URL: http://www.ltg.ed.ac.uk/~ht/ [mail really from me _always_ has this .sig -- mail without it is forged spam] -BEGIN PGP SIGNATURE- Version: GnuPG v1.2.6 (GNU/Linux) iD8DBQFDQsXwkjnJixAXWBoRAtFkAJ4nfhtZSR59psSEgCsDt4cvul0NWQCfe6fK BGPNeN3KI0vKRG4H8PGCDPI= =yZ68 -END PGP SIGNATURE- ___ Dashboard-hackers mailing list Dashboard-hackers@gnome.org http://mail.gnome.org/mailman/listinfo/dashboard-hackers
Re: Beagle 0.1.1
On Tue, 2005-10-04 at 16:00 +, Charlie Law wrote: > On Tue, 04 Oct 2005 11:43:59 -0400 > Jon Trowbridge <[EMAIL PROTECTED]> wrote: > > > On Tue, 2005-10-04 at 15:36 +, Charlie Law wrote: > > > Has the Beagle wiki site been hijacked? I get a page about Banshee > > > music file sharing. > > > > www.beagle-project.org looks OK to me. Is anyone else seeing this? > > > It must have been a local reroute of some kind. If I log on through a VPN, I > get a good beagle page. When I log on to the site without the VPN, I get a > page about Banshee file sharing. > > I'm on an unfamiliar network right now, so I suspect there's something > strange. But it appears to be local, not general. Yeah - this could be caused by some crack proxy that strips out the 'Host' header or something similar. It seems that www.banshee- project.org and www.beagle-project.org are hosted on the same machine (64.14.94.162) and just going to that IP address (http://64.14.94.162) takes me to the bansee site. So, without the 'Host' header the web server doesn't know which site you want and just gives you the banshee page. Of course, I don't know why there would be a proxy that strips out that header, but that is what makes it a crack proxy. Mark. > ___ > Dashboard-hackers mailing list > Dashboard-hackers@gnome.org > http://mail.gnome.org/mailman/listinfo/dashboard-hackers signature.asc Description: This is a digitally signed message part ___ Dashboard-hackers mailing list Dashboard-hackers@gnome.org http://mail.gnome.org/mailman/listinfo/dashboard-hackers
Re: Beagle 0.1.1
> That's not unreasonable, of course, but it's not recursing, and so is > looping very fast! That is, it's not actually indexing any files, > which are all in subdirectories. . . I also noticed similar behaviour - wait for some time - it takes a while for the file system backend to find the subdirectories and actually index the files in them. On second thought, probably the poll time for non-inotify case shouldnt be that low. - d. ___ Dashboard-hackers mailing list Dashboard-hackers@gnome.org http://mail.gnome.org/mailman/listinfo/dashboard-hackers
Re: Beagle 0.1.1
On Tue, 04 Oct 2005 11:43:59 -0400 Jon Trowbridge <[EMAIL PROTECTED]> wrote: > On Tue, 2005-10-04 at 15:36 +, Charlie Law wrote: > > Has the Beagle wiki site been hijacked? I get a page about Banshee > > music file sharing. > > www.beagle-project.org looks OK to me. Is anyone else seeing this? > It must have been a local reroute of some kind. If I log on through a VPN, I get a good beagle page. When I log on to the site without the VPN, I get a page about Banshee file sharing. I'm on an unfamiliar network right now, so I suspect there's something strange. But it appears to be local, not general. ___ Dashboard-hackers mailing list Dashboard-hackers@gnome.org http://mail.gnome.org/mailman/listinfo/dashboard-hackers
Re: Beagle 0.1.1
Nope... this wiki history seems clean.. dav Jon Trowbridge writes: > On Tue, 2005-10-04 at 15:36 +, Charlie Law wrote: > > Has the Beagle wiki site been hijacked? I get a page about Banshee > > music file sharing. > > www.beagle-project.org looks OK to me. Is anyone else seeing this? > > -J > > > ___ > Dashboard-hackers mailing list > Dashboard-hackers@gnome.org > http://mail.gnome.org/mailman/listinfo/dashboard-hackers > ___ Dashboard-hackers mailing list Dashboard-hackers@gnome.org http://mail.gnome.org/mailman/listinfo/dashboard-hackers
Re: Beagle 0.1.1
On 10/4/05, Jon Trowbridge <[EMAIL PROTECTED]> wrote: > On Tue, 2005-10-04 at 15:36 +, Charlie Law wrote: > > Has the Beagle wiki site been hijacked? I get a page about Banshee > > music file sharing. > > www.beagle-project.org looks OK to me. Is anyone else seeing this? No, beaglewiki.org and beagle-project.org both look OK. -Tom ___ Dashboard-hackers mailing list Dashboard-hackers@gnome.org http://mail.gnome.org/mailman/listinfo/dashboard-hackers
Re: Beagle 0.1.1
On Tue, 2005-10-04 at 15:36 +, Charlie Law wrote: > Has the Beagle wiki site been hijacked? I get a page about Banshee > music file sharing. www.beagle-project.org looks OK to me. Is anyone else seeing this? -J ___ Dashboard-hackers mailing list Dashboard-hackers@gnome.org http://mail.gnome.org/mailman/listinfo/dashboard-hackers
Re: Beagle 0.1.1
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Jon Trowbridge writes: > The looping that you have observed is probably not a bug. When inotify > is not available, Beagle has to keep re-crawling the file system to look > for changes. I suspect that is what is happening here. That's not unreasonable, of course, but it's not recursing, and so is looping very fast! That is, it's not actually indexing any files, which are all in subdirectories. . . ht - -- Henry S. Thompson, HCRC Language Technology Group, University of Edinburgh Half-time member of W3C Team 2 Buccleuch Place, Edinburgh EH8 9LW, SCOTLAND -- (44) 131 650-4440 Fax: (44) 131 650-4587, e-mail: [EMAIL PROTECTED] URL: http://www.ltg.ed.ac.uk/~ht/ [mail really from me _always_ has this .sig -- mail without it is forged spam] -BEGIN PGP SIGNATURE- Version: GnuPG v1.2.6 (GNU/Linux) iD8DBQFDQqL3kjnJixAXWBoRAqYiAJ9JETCkWDRbORF9KoVPWhT3PtZzOQCfZ8MO KNNdR3Jb0zzCK9hP5+/Dc8U= =mKok -END PGP SIGNATURE- ___ Dashboard-hackers mailing list Dashboard-hackers@gnome.org http://mail.gnome.org/mailman/listinfo/dashboard-hackers
Re: Beagle 0.1.1
Has the Beagle wiki site been hijacked? I get a page about Banshee music file sharing. On Mon, 03 Oct 2005 18:17:15 -0400 Jon Trowbridge <[EMAIL PROTECTED]> wrote: > > I'm pleased to announce the release of Beagle 0.1.1. > > This version contains fixes for a number of bugs and one major new feature: > a new KMail backend written by the redoubtable D Bera. > > > OUR MANY URLS > - > > To download the 0.1.1 tarball or learn more, visit the Beagle wiki at: > http://www.beagle-project.org > > Joe Gasiorek writes a Beagle newsletter. You can read it at: > http://www.beagle-project.org/Newsletter > > The latest gossip is available at: > http://www.planetbeagle.org > > Nat Friedman made some cool movies that demonstrate Beagle in action: > http://nat.org/demos > > We still talk about Beagle on the dashboard-hackers mailing list: > http://mail.gnome.org/mailman/listinfo/dashboard-hackers > > George Washington, Alexander Hamilton and James Madison (among others) > were granted honorary French citizenship during the French Revolution. > http://en.wikipedia.org/wiki/List_of_people_granted_honorary_French_citizenship_during_the_French_Revolution > > > WHAT IS BEAGLE? > --- > > Beagle is a tool for indexing and searching your data. Beagle is improving > rapidly on many fronts, and should work well enough for everyday use. > > The Beagle daemon transparently monitors your data and updates the index > to reflect any changes. On an inotify-enabled system, these updates happen > more-or-less in real time. So for example, > > * Files are immediately indexed when they are created, are re-indexed > when they are modified, and are dropped from the index upon > deletion. > * E-mails are indexed upon arrival. > * IM conversations are indexed as you chat, a line at a time. > > Beagle uses the Lucene indexing system from the prodigious Doug > Cutting. > > Best is a graphical tool for searching the index that the daemon creates. > Best doesn't query the index directly; it passes the search terms to the > daemon and the daemon sends any matches back to Best. Best then renders the > results and allows you to perform useful actions on the matching objects. > > Indexing your data requires a fair amount of computing power, but the Beagle > daemon tries to be as unobtrusive as possible. It contains a scheduler that > works to prioritize tasks and control CPU usage, based on whether or not > you are actively using your workstation. > > > DEPENDENCY HECK > --- > > Beagle has many dependencies, and thus can be difficult to compile. > It requires: > * Mono 1.1.7 or better, along with the full Mono stack > * gtk-sharp 1.9.5 or better > * Gecko-sharp 2.0 > * Gmime 2.1.16 > * Libexif 0.5.7 or better > > For the best possible Beagle experience, you should also have: > * Evolution-sharp 0.10.2 > * A *patched* wv 1.0.3 --- the patch is available from > http://users.avafan.com/~fredrik/beagle/wv-libole2-readonly.patch > * An inotify 0.24-enabled kernel. Inotify is in the mainline Linux > kernel as of 2.6.13. > > > CHANGES SINCE 0.1.0 > --- > > Daemon/Infrastructure: > * Keep track of the number of tasks we've processed in a given run > through the scheulder and yield if we pass a threshold from the CPU > stuff. (Joe) > * Add a new task type which removes all items which match a certain > property. (Joe) > * Fixed leaking index file descriptors. (Daniel Drake) > * Force the encoding of XmlSerializer to be UTF-8 since it defaults to > the current system encoding. (Joe) > > Backends: > * Initial KMail support. (D Bera) > * Fix an exception in the file system backend when trying to ignore > paths whose parent wasn't also being watched. (Lukas Lipka, Joe) > * Correctly handle removed items in the Evolution Data Server backend. > (Joe) > * Use a new URI scheme that is compatible with Evolution 2.4, so that > calendar items and contacts can be opened in Evo. (Joe, Lukas) > * Fix an exception in the Gaim backend when not using inotify. (Joe) > * Rename the IMLog backend to GaimLog. (Lukas) > * Better handling of directories with exotic permissions in the file > system backend. (Jon Trowbridge) > > Filters: > * Add a bunch of special text mime types found in shared-mime-info for > the plain text filter. (Joe) > * Support OOo Draw files in OpenOffice filter. (David Richards) > > UI/Tools: > * Fix an exception that would show up if you used beagle-index-url when > the IndexingService backend wasn't enabled. (Joe) > * Allow best to start beagled on amd64. (Jack Miller) > > Translations: > * Updated Bulgarian translation. (Alexander Shopov) > * Updated Chinese translation. (fwang) > * Updated Dutch translation. (Wouter Bolsterlee) > * Updated German translation. (Hendrik Brandt) > * Updated Japanese translation. (Takeshi AIHANA) > * Updated Vietnamese translation. (clyties) > > Everything Else: > * Build the Evolution Data Server ba
Re: Beagle 0.1.1
> Previous problem persists, minor change -- loops now w/o setting > BEAGLE_EXERCISE_THE_DOG: > inotify_init: Function not implemented > Inotify not supported! You need a 2.6.13 kernel or later with > CONFIG_INOTIFY enabled.WARN: Could not initialize inotify ^ Without inotify, looping is expected. > DEBUG: Daemon initialization finished after 2.18s > DEBUG: Done crawling '/disk/b' > DEBUG: Done crawling '/disk/b' > DEBUG: Done crawling '/disk/b' > DEBUG: Done crawling '/disk/b' ___ Dashboard-hackers mailing list Dashboard-hackers@gnome.org http://mail.gnome.org/mailman/listinfo/dashboard-hackers
Re: Beagle 0.1.1
On Tue, 2005-10-04 at 15:52 +0100, Henry S. Thompson wrote: > inotify_init: Function not implemented > Inotify not supported! You need a 2.6.13 kernel or later with > CONFIG_INOTIFY enabled.WARN: Could not initialize inotify The looping that you have observed is probably not a bug. When inotify is not available, Beagle has to keep re-crawling the file system to look for changes. I suspect that is what is happening here. -J ___ Dashboard-hackers mailing list Dashboard-hackers@gnome.org http://mail.gnome.org/mailman/listinfo/dashboard-hackers
Re: Beagle 0.1.1
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Built and installed new release. Previous problem persists, minor change -- loops now w/o setting BEAGLE_EXERCISE_THE_DOG: Note that extended attributes _are_ supported on the (local) /disk/b filesystem, although my home dir is on NFS. /home/ht> beagled --web-root /home/ht/.beagle/webroot/ --deny-backend mail - --deny-backend EvolutionDataServer --debug --fg INFO: Starting Beagle Daemon (version 0.1.1) DEBUG: Command Line: /group/ltg/projects/lcontrib9/lib/beagle/BeagleDaemon.exe --web-root /home/ht/.beagle/webroot/ --deny-backend mail --deny-backend EvolutionDataServer --debug --fg WARN: Extended attributes are not supported on this filesystem. Many search backends will not be available DEBUG: Starting main loop DEBUG: Starting messaging server DEBUG: Loading Beagle.Util.Conf+IndexingConfig from indexing.xml DEBUG: Initializing index synchronization DEBUG: Synchronizing... (target=Local) DEBUG: Synchronized successfully in .16s DEBUG: Starting QueryDriver DEBUG: Found 0 types in EvolutionDataServer, Version=0.0.0.0, Culture=neutral DEBUG: Found index helper at /group/ltg/projects/lcontrib9/lib/beagle/beagled-index-helper INFO: KMail folders not found. Will keep trying inotify_init: Function not implemented Inotify not supported! You need a 2.6.13 kernel or later with CONFIG_INOTIFY enabled.WARN: Could not initialize inotify DEBUG: Starting FileSystemWatcher Backend DEBUG: Found 11 types in BeagleDaemonLib, Version=1.4.3.3, Culture=neutral DEBUG: Found 0 user-configured static queryables DEBUG: Adding root: /disk/b DEBUG: Loaded 0 records from /tmp/beagle-ht-a6be612b-04b8-4ce6-9a16-e00cdc761a40/Indexes/FileSystemIndex/FileAttributesStore.db in 0.000s DEBUG: Done starting FileSystemQueryable INFO: Starting KMail backend DEBUG: Starting Scheduler thread DEBUG: KMail directories (local mail) /home/ht/.kde/share/apps/kmail/dimap not found, will repoll. INFO: This Computer Hostname: erasmus.inf.ed.ac.uk DEBUG: Starting WebBackEnd INFO: Starting WebServiceBackEnd DEBUG: Global WebServicesAccess Enabled DEBUG: Starting Internal Web Server BeagleXsp Listening on port: Listening on address: 0.0.0.0 Root directory: /amd/nfs/pegasus/disk/ptn051/ht/.beagle/webroot DEBUG: BeagleXSP Applications list: /:/home/ht/.beagle/webroot/,/beagle:/home/ht/.beagle/webroot//beagle,/beagle/local:/group/ltg/projects/lcontrib9,/beagle/gnome:/usr,/beagle/kde3:/usr,/beagle/img:/home/ht/.beagle/img DEBUG: Daemon initialization finished after 2.18s DEBUG: Done crawling '/disk/b' DEBUG: Done crawling '/disk/b' DEBUG: Done crawling '/disk/b' DEBUG: Done crawling '/disk/b' ... - -- Henry S. Thompson, HCRC Language Technology Group, University of Edinburgh Half-time member of W3C Team 2 Buccleuch Place, Edinburgh EH8 9LW, SCOTLAND -- (44) 131 650-4440 Fax: (44) 131 650-4587, e-mail: [EMAIL PROTECTED] URL: http://www.ltg.ed.ac.uk/~ht/ [mail really from me _always_ has this .sig -- mail without it is forged spam] -BEGIN PGP SIGNATURE- Version: GnuPG v1.2.6 (GNU/Linux) iD8DBQFDQpcckjnJixAXWBoRAnTRAJ4mjWNIB3vq1wVvOZ+EqlLttuLRGACggElk dR92AmERmTFOirLEMdO5/NI= =0l0u -END PGP SIGNATURE- ___ Dashboard-hackers mailing list Dashboard-hackers@gnome.org http://mail.gnome.org/mailman/listinfo/dashboard-hackers
