Re: Beagle with Samba Share
From: D Bera [EMAIL PROTECTED] at (wrapper managed-to-native) Mono.Data.SqliteClient.Sqlite.sqlite3_step (intptr) 0x4 The problems could be related to file locking. Such issues have cropped up with nfs mounted filesystems in the past. samba forums pointed to some weirdos using sqlite on samba shares. Maybe this is related http://www.mail-archive.com/sqlite-users@sqlite.org/msg20409.html http://lists.samba.org/archive/linux-cifs-client/2006-November/001583.html I've tried specifying nobrl in the mount command but the problem still occurs. Joe: In answer to your question, yes all other apps work fine (so far). I guess it's pretty likely that it's a SQLite problem with Samba shares. One of the above links mentions a fix in 2.6.19, so I could test again in the future. Thanks for the information... ** Information in this message may contain confidential and privileged information. If you are not the intended recipient please accept our apologies; please do not disclose, copy or distribute information in this e-mail or take any action in reliance on its contents: to do so is strictly prohibited and may be unlawful. Please inform us that this message has gone astray before deleting it. Thank you for your co-operation. NHSmail is used daily by over 100,000 staff in the NHS. Over a million messages are sent every day by the system. To find out why more and more NHS personnel are switching to this NHS Connecting for Health system please visit www.connectingforhealth.nhs.uk/nhsmail ** ___ Dashboard-hackers mailing list Dashboard-hackers@gnome.org http://mail.gnome.org/mailman/listinfo/dashboard-hackers
Re: firefox extension
Hi, On Fri, 2007-01-19 at 07:35 +0100, Bernhard Kleine wrote: on my debian desktop, i am using beagle (actually the very reason why i have the unstable distribution). The firefox derivative Iceweasel 2.0.0.1 is not supported by the Beagle Indexer 0.5. Is there any hope that this lack of support will go away soon? Use 0.6. It has support for Firefox 2.0, so I think it'll work with Iceweasel. http://beagle-project.org/Firefox_Extension Joe ___ Dashboard-hackers mailing list Dashboard-hackers@gnome.org http://mail.gnome.org/mailman/listinfo/dashboard-hackers
Re: Beagle with Samba Share
Hi, On Fri, 2007-01-19 at 15:18 +, Stringer Leon (West Midlands Ambulance Service NHS Trust) wrote: I guess it's pretty likely that it's a SQLite problem with Samba shares. One of the above links mentions a fix in 2.6.19, so I could test again in the future. It seems that way. This is the first I've heard of such a problem. You may have mentioned before, but what distribution are you using? Beagle can use sqlite 3.3.1 or greater as well as 2.x, so that is greatly preferable. It's a build-time decision, though, and different distros build it differently. You may be able to rebuild the package so that it uses sqlite3 if you are brave. :) (FWIW, I am considering dropping support for sqlite 2.x in the not-too-distant future.) Joe ___ Dashboard-hackers mailing list Dashboard-hackers@gnome.org http://mail.gnome.org/mailman/listinfo/dashboard-hackers
Re: beagle - can it clean up after itself?
Beagle is 0.2.14. It's boring to examine hundreds of files, but from samples it's safe to say they're all products of beagle and seem mainly to be contents of zip files (or perhaps other archives, too?). Meanwhile, after ~/.beagle/TextCache completely filled up my hard drive, I deleted ~/.beagle and started over from scratch. So far, so good. Thanks to all who replied. Debajyoti Bera writes: 1. I've noticed that beagle fills my /tmp directory with scores of files named according to the pattern tmpxxx.tmp. When can these be safely deleted, and can beagle take care of doing that itself? Beagle is supposed to automatically delete them. When beagle is not running, there should not be any tmp*.tmp files in the /tmp directory. Those can be safely deleted when beagle is not running. In fact, if there are tmp files then its is a serious BUG. Hmmm... I just looked in my /tmp and found about 240 of these files. I just ran beagle-shutdown and those files are still there. Using the command, 'du -hc tmp*tmp' shows me that they total about 8.3MB. Which beagle version do you have ? And what kind of files are those ? I mean, do they look like emails, email attachments, contents of some zip file ? I guess they are emails or email attachments, but please check. If they are email related, which email client do you use ? ___ Dashboard-hackers mailing list Dashboard-hackers@gnome.org http://mail.gnome.org/mailman/listinfo/dashboard-hackers
Re: beagle - can it clean up after itself?
Joe Shaw writes: On Thu, 2007-01-18 at 12:08 -0500, Michael Blaustein wrote: 2. Same question about files in .beagle/TextCache - can they be safely deleted; if so, when; and can beagle do this itself? This is a serious issue for me, since this directory is rapidly exhausting my hard drive space. They can be deleted, but it means that you won't have snippets in most search results. I don't know what snippets are in this context. 3. Is there any way for a user to control the amount of memory beagle (really beagled-helper) takes up? Every time I start beagle, by rebooting or by loggin on to my account, there is a longish time when indexing takes up 50-60 percent or more of memory, and as a result no other process can run reasonably responsively. (exercise_the_dog is not set.) The beagle-helper process monitors its own memory usage and if it crosses a threshold it will shut itself down and restart at the end of the current batch of indexing. If you're seeing extended periods of time where the memory usage is pretty high (and never going back down), you're probably hitting a bug in one of the file filters. Examining the index helper logs might help identify the problematic file. Yes! It seems (so far) that a bad MSWord file was responsible for all the memory hogging. It might be nice if beagle learned to handle this more gracefully; of course, I deleted that file . . . Thanks for all the explanations. ___ Dashboard-hackers mailing list Dashboard-hackers@gnome.org http://mail.gnome.org/mailman/listinfo/dashboard-hackers
MS Word (.doc) processing moved out of process
Hi, I just committed code which moves our processing of MS Word documents out of process, which should hopefully increase the reliability of Beagle quite a bit on systems which have troublesome documents. If you were using external filters to get around these crashes, if you run out of SVN you can disable them. I've also added code to limit the ability of externally run helpers (like the new .doc extractor, pdftotext, rpm, etc.) to run away with the CPU or memory. I would greatly appreciate it if people could check out of SVN and test these things, and if they're pretty bug free, we can do an 0.2.15 release soon. Thanks! Joe ___ Dashboard-hackers mailing list Dashboard-hackers@gnome.org http://mail.gnome.org/mailman/listinfo/dashboard-hackers
Re: MS Word (.doc) processing moved out of process
If you were using external filters to get around these crashes, if you run out of SVN you can disable them. Well, to be specific, now the bad word files would not crash beagle anymore. If wv crashes, then it would crash the beagle-doc-extractor tool which runs outside of beagle. However, that means your doc file text won't get indexed :-(. There are doc2text tools out there which can successfully extract text out of docs for which wv crashes - if you are using any of them in your external filter you might want to continue using them. Test your doc files with beagle-extract-content or beagle-doc-extractor. If they work, good. If don't, keep using one of the other doc text extraction tool out there. But please a file a bug or leave a comment in the already filed bugs in wv bugzilla (http://bugzilla.abisource.com/). Those are bugs which should be fixed. The sooner the better. - dBera -- - Debajyoti Bera @ http://dtecht.blogspot.com beagle / KDE fan Mandriva / Inspiron-1100 user ___ Dashboard-hackers mailing list Dashboard-hackers@gnome.org http://mail.gnome.org/mailman/listinfo/dashboard-hackers
Re: MS Word (.doc) processing moved out of process
wv should be pretty reliable - if it's not, bug reports are _very much_ appreciated because the code is used all over the place, including (dear to my heart) AbiWord, and it shouldn't crash. Sample documents are greatly appreciated. How about http://bugzilla.abisource.com/show_bug.cgi?id=10025 ? (it was submitted by beagle doc filter author) - dBera -- - Debajyoti Bera @ http://dtecht.blogspot.com beagle / KDE fan Mandriva / Inspiron-1100 user ___ Dashboard-hackers mailing list Dashboard-hackers@gnome.org http://mail.gnome.org/mailman/listinfo/dashboard-hackers
Re: MS Word (.doc) processing moved out of process
There are doc2text tools out there which can successfully extract text out of docs for which wv crashes - if you are using any of them in your external filter you might want to continue using them. What are the tools? We might want to just use them instead of our own beagle-doc-extractor if they're more reliable. I dont remember precisely what I used to use before but I think it was antiword. - dBera -- - Debajyoti Bera @ http://dtecht.blogspot.com beagle / KDE fan Mandriva / Inspiron-1100 user ___ Dashboard-hackers mailing list Dashboard-hackers@gnome.org http://mail.gnome.org/mailman/listinfo/dashboard-hackers
