Thank you for taking the time to report this bug and helping to make
Ubuntu better. As far as i now beagle development was stopped 2010. I
will close this bug report.
** Changed in: beagle (Ubuntu)
Status: Confirmed = Invalid
--
You received this bug notification because you are a member
(Sorry for the double post, clicked save by accident)
Have there been any updates?
--
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 subscribed to Ubuntu.
Erm.. it's been over a year and nothing has been done about this...
--
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 subscribed to Ubuntu.
--
** Changed in: beagle (Ubuntu)
Importance: Undecided = Medium
--
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.
--
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
if the situation is this, the file have to be moved from cron.dayly to
cron.weekly at least, in my opinion...
--
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,
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
ok wait, there are 2 indexing processes. the first indexes
applications (and it lasts in few minutes) and the second indexes
documentation (that one is very long)
I'm attaching the application indexing log, as I think that it is
enough to understand the bug
--
beagle-build-index uses 100% of cpu
the cpu is always used at 100%, no matter which file is indexed.
since the index operation will always last more than 20 minutes I
think that the index is completely rebuildt every time. I'm doing the
log files now.
There are some errors when trying to index screensaver files (the
extension is
the two files are very similar. so I think that the index is deleted and
rebuilt without any check
** Attachment added: build-index.1
http://librarian.launchpad.net/7683020/build-index.1
--
beagle-build-index uses 100% of cpu when started from cron.daily
https://bugs.launchpad.net/bugs/89487
** Attachment added: build-index.2
http://librarian.launchpad.net/7683022/build-index.2
--
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
Actually, I would rather see the documentation one.
The application is working ok. The reason you see files being repeated
is, build-index does not have any filter (parser) for screensaver
desktop files, so when the indexer gets such a file it says Error:
Could not filter file: No desktop entry
so do you mean that every time beagle tries to index the files that
didn't manage to index the previous time, because of missing filters?
if so this might be the problem with documentation files, maybe every
time he tries to index those files, but it doesn't have the correct
filter...
And this
** Attachment added: documentation-index.1
http://librarian.launchpad.net/7686858/documentation-index.1
--
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
** Attachment added: documentation-index.2
http://librarian.launchpad.net/7686859/documentation-index.2
--
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
this is the line to start the documentation index (start it from the
user beagleindex)
/usr/sbin/beagle-build-index --target
/var/cache/beagle/indexes/documentation --disable-directories
--recursive --allow-pattern *.xml,*.html,*.docbook /usr/share/doc
/usr/local/share/doc /opt/kde3/share/doc
in the cron launcher there is also a reference to a binary called ionice from
the universe package schedutils
maybe this binary let the process to be executed with less resource greed... I
have not tested it yet
--
beagle-build-index uses 100% of cpu when started from cron.daily
Yeah, the ionice is supposed to lower the io priority. Actually, if you check
the first two lines of the log, you will see Debug: Set best effort IO
priority to lowest level (7)
Debug: Reniced process to 19 - which means beagle is already trying to play
fare.
Could you attach one of the
there are some strange characters (non european)... could it be this?
--
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.
--
** Attachment added: legal.xml
http://librarian.launchpad.net/7687290/legal.xml
--
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
here is another file
** Attachment added: legal.xml
http://librarian.launchpad.net/7687299/legal.xml
--
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
I figured out the problem. The docbook parser is failing to parse those
files, thus those files are getting filtered again on re-indexing. It
really cannot be avoided, since users can always install updated filters
before re-running build-index.
The bad thing is that the docbook filter decides
all right... so we just need to wait...
--
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
23 matches
Mail list logo
