After an evaluation, GNOME has moved from Bugzilla to GitLab. Learn more about GitLab.
No new issues can be reported in GNOME Bugzilla anymore.
To report an issue in a GNOME project, go to GNOME GitLab.
Do not go to GNOME Gitlab for: Bluefish, Doxygen, GnuCash, GStreamer, java-gnome, LDTP, NetworkManager, Tomboy.
Bug 169691 - beagled keeps on indexing only 2 files in the home directory
beagled keeps on indexing only 2 files in the home directory
Status: RESOLVED INVALID
Product: beagle
Classification: Other
Component: General
0.0.x
Other Linux
: Normal normal
: Milestone 1
Assigned To: Jon Trowbridge
Jon Trowbridge
Depends on:
Blocks:
 
 
Reported: 2005-03-09 08:55 UTC by Subodh Soni
Modified: 2005-03-18 05:02 UTC
See Also:
GNOME target: ---
GNOME version: ---

Attachments
beagled log from .beagle/Log/ directory (148.59 KB, text/plain)
2005-03-10 08:09 UTC, Subodh Soni 		Details

Description Subodh Soni 2005-03-09 08:55:40 UTC 
Distribution/Version: SuSE 9.3

1. I have many directories under my $HOME with many files in those dirs.
2. I start beagled with --fg and --debug options.
3. Over some period of time and create/edit/delete many files while the beagled
is running.
4. I have observed in the DEBUG messages that only 2 files are being indexed and
re-indexed continuously.
5. In spite of the files being un-touched and un-modified beagled keeps on
indexing those 2 files. In addition to it, beagled is not indexing other files
in my home directory (i.e. it is not even picking up the other files for indexing)
6. I am pasting a part of the debug log (that I get on console) showing the 2
files that are being picked up for indexing (the same log keeps on repeating)

---------- DEBUG LOG START ------------------------
DEBUG: - file:///home/subodh/Beagle/beagle-status-07-March-2005
DEBUG: + file:///home/subodh/Beagle/beagle-status-07-March-2005
DEBUG: CloseIfQueued on FileSystemIndex
DEBUG: Flush Complete!
DEBUG: CloseIfQueued on FileSystemIndex
DEBUG: Close on FileSystemIndex
DEBUG: Open on FileSystemIndex
DEBUG: Launching flush thread!
DEBUG: CloseIfQueued on FileSystemIndex
DEBUG: Flush Complete!
DEBUG: Close on FileSystemIndex
DEBUG: CloseIfQueued on FileSystemIndex
DEBUG: Open on FileSystemIndex
DEBUG: Close on FileSystemIndex
DEBUG: Open on FileSystemIndex
DEBUG: Launching flush thread!
DEBUG: Flushing...
DEBUG: - file:///home/subodh/suse/mono-devel-1.1.4-1.ximian.10.1.i586.rpm
DEBUG: + file:///home/subodh/suse/mono-devel-1.1.4-1.ximian.10.1.i586.rpm
DEBUG: CloseIfQueued on FileSystemIndex
DEBUG: Flush Complete!
DEBUG: CloseIfQueued on FileSystemIndex
DEBUG: Close on FileSystemIndex
DEBUG: Open on FileSystemIndex
DEBUG: Launching flush thread!
DEBUG: CloseIfQueued on FileSystemIndex
DEBUG: Flush Complete!
DEBUG: CloseIfQueued on FileSystemIndex
DEBUG: Close on FileSystemIndex
---------- DEBUG LOG END ------------------------

The files beagle-status-07-March-2005 & mono-devel-1.1.4-1.ximian.10.1.i586.rpm
are not at all modified OR touched from a long time.
Comment 1 Jon Trowbridge 2005-03-09 19:28:03 UTC 
Could you please get me the complete beagled log and the last helper log?
Comment 2 Subodh Soni 2005-03-10 08:08:29 UTC 
Jon: I am attaching the beagled log but there is no last helper log in the
.beagle/ directory. I am running beagle on SuSE 9.3 beta1 and there isn't any
helper log file created in .beagle/ directory.
Comment 3 Subodh Soni 2005-03-10 08:09:41 UTC 
Created attachment 38492 [details]
beagled log from .beagle/Log/ directory
Comment 4 Jon Trowbridge 2005-03-18 05:02:29 UTC 
I'm not able to reproduce this.  Closing as INVALID, please re-open if you
continue to see the problem.