I can verify all of the above This major annoyance (seems a bit harsh to call it a bug though :) is especially frustrating in an LTSP environment.
Firstly because the hardware even for fat clients usually is quite modest in terms of performance, and second (which is worst) the process is absolutely unnecessary when running the clients. All updates to the clientss is done manually via chroot and the image update or build process. In chroot and update I point to the index on the server itself which most people do. As far as I can tell this cronjob is started as a separate process for all clients booted, fat as thin, and it seems that it is always "due" for updating even if you just do a 45 second reboot of your client (guess there is nothing there to tell the client it has been done) This means you either put the server to a grinding halt when starting 20+ clients in the morning (naturally depending on your server specs), or your fat clients spend between 2 and ten (!) minutes at often near 100% CPU utilization updating an index that is probably sent to dev null or purged when the client is switched of (don't know, haven't investigated what happens with it) The "Fix" helps (however i've choosen to purge apt-xapian-index completely in the client chroot, cant see a reason not to) Not sure if this should go upstream.. Am a newbie when it comes to bug reporting so; copy and paste if you think the folks @ ltsp or someone else should take a look at this aswell. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/830333 Title: randomly, update-apt-xapi will take 100% cpu for an extended period of time To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apt-xapian-index/+bug/830333/+subscriptions -- ubuntu-bugs mailing list [email protected] https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
