the strange thing is that it seems that the index builder removes files and readds them into the index:
Debug: -file:///usr/share/doc/python/python-policy.html/ap-build_dependencies.html [.....] Debug: +file:///usr/share/doc/python/python-policy.html/ap-build_dependencies.html this is why it always use lots of cpu... it does not check if the file had been already indexed! ** Summary changed: - beagle-build-index hangs and must be killed + beagle-build-index uses 100% of cpu when started from cron.daily ** Description changed: Binary package hint: beagle - When the cron job to build the indexes start beagle-build-index will - hang and take up as much CPU as it can. SIGTERM will not stop the - process, it must get SIGKILL to actually quit. + When the cron job to build the indexes start beagle-build-index will take up as much CPU as it can. SIGTERM will not stop the process, it must get SIGKILL to actually quit. + It is not hanged but the indexing process is very resource intensive Version: 0.2.16-0ubuntu4 ProblemType: Bug Date: Sat Mar 3 16:54:32 2007 DistroRelease: Ubuntu 7.04 Uname: Linux othello.oyving.org 2.6.20-9-generic #2 SMP Sun Feb 25 22:59:06 UTC 2007 x86_64 GNU/Linux -- 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
