> fyo, do you mean this statement: > > - do not modify the DB "in-place" with --update to avoid > > software-center seeing a corrupted database when it has > > it open at the same time
Yes, that appears to be the argument for removing --update, which was otherwise added in an upstream patch. It is unfortunate that update-apt-xapian-index resource use is increased many-fold due to Software Center not (gracefully) handling an in- progress update. Depending on the nature of the Software Center issue, this choice is perhaps understandable. I should note that I was NOT able to reproduce any issue with Software Center while running update-apt-xapian-index --update. The closest thing I could get was a 10 second "animated loading ring" coinciding with the update process being at 99% (any io heavy activity could probably give that result, though). -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/363695 Title: update-apt-xapian-index uses too much CPU and memory To manage notifications about this bug go to: https://bugs.launchpad.net/apt/+bug/363695/+subscriptions -- ubuntu-bugs mailing list [email protected] https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
