> lm-profiler is useless if you look at the disk light / load cycles. It > does a lot of its own stuff with the disk, so the disk activity you're > seeing is most probably caused by lm-profiler itself.
No, I was not running lm-profiler the second time around after I closed kdpf and measured the load cycles. I should have made this clearer, and I apologize for the confusion. To clarify: lm-profiler indicated that kpdf was responsible for accessing the disk during an idle period. To test whether kpdf indeed was the culprit, I closed the application and then let the system sit idle for 5 minutes *without running lm- profiler*. During those 5 minutes, I observed periodic disk activity, and the load cycle increased. This cannot have been caused by lm-profiler, as it was not running, so something else must be responsible; something that does not show up in lm-profiler. -- Hard drive spindown should be configurable https://bugs.launchpad.net/bugs/17216 You received this bug notification because you are a member of Ubuntu Bugs, which is a direct subscriber. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
