> the strange thing is that it seems that the index builder removes > files and readds them into the index
Beagle is supposed to check if a file is already indexed, if not it prints the -file:/// and +file:/// and proceeds to add the file to the index. The actual file is indexed between these two lines, the -file:/// last printed will tell you which file is being currently indexed. So, (1) by observing the output during 100% cpu can you find out which document is taking up all the CPU. Possibly is a bug in some beagle file parser. (2) Do you think beagle is re-adding some files that it indexed before and the file was not changed in between ? Some bug could have been introduced here lately. Can you output two consequtive runs of beagle-build-index to some log file and attach it here/send it to me ? -- beagle-build-index uses 100% of cpu when started from cron.daily https://bugs.launchpad.net/bugs/89487 You received this bug notification because you are a member of Ubuntu Bugs, which is the bug contact for Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
