"Joe Shaw" <joe@joeshaw.org> writes:
Scheduler: Count: 278 Status: Executing task Delayed 0 (8/22/2007 1:45:38 PM) Crawling /suse/ke/News/cache/nnimap+suse:INBOX.cestina
Pending Tasks: 1 Immediate 0 (8/22/2007 1:48:09 PM) http://skillingstad.no/packages/
The question here really is: does this change over time, say, 5 minutes?
It did not change since yesterday.
If not, you've found a bug; sending SIGUSR2 to the beagled-helper process will cause beagle to log to its ~/.beagle/Log/current-IndexHelper file which file it's working on. With that information, you can run the beagle-extract-content tool on that file and see if it too hangs. Then I just need to debug *why* that behavior happens for that specific file.
I killed the helper (and it automatically restarts): cat ~/.beagle/Log/current-IndexHelper 070823 1045232558 10887 IndexH WARN: Unable to set IO priority for process to idle 070823 1045234664 10887 IndexH WARN: Found a dangling index lock on /tmp/beagle-ke-9eebda98-f387-48f9-8822-0458da787257/Indexes/FileSystemIndex/Locks/lucene-640d6e228eb98de51dad5df57cf08693-write.lock beagle-extract-content /tmp/beagle-ke-9eebda98-f387-48f9-8822-0458da787257/Indexes/FileSystemIndex/Locks/lucene-640d6e228eb98de51dad5df57cf08693-write.lock Filename: file:///tmp/beagle-ke-9eebda98-f387-48f9-8822-0458da787257/Indexes/FileSystemIndex/Locks/lucene-640d6e228eb98de51dad5df57cf08693-write.lock Debug: Loaded 50 filters from /usr/lib/beagle/Filters/Filters.dll Filter: Beagle.Filters.FilterText MimeType: text/plain Properties: Timestamp = 8/23/2007 8:45:23 AM Content: 10887 (no hot content) Maybe, that's what you need. -- Karl Eichwalder R&D / Documentation SUSE LINUX Products GmbH, GF: Markus Rex, HRB 16746 (AG Nuernberg) -- To unsubscribe, e-mail: opensuse-gnome+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-gnome+help@opensuse.org