Quote:
Originally Posted by Ffan
So I just entered some gibberish into the search, all I can see happening is the little "ring"-thingy in the top left corner spinning, nothing else really.
|
Not the expected behavior.
But does indicate that the indexer is somehow "lost" in its job and that the problem is of the same age of the book(s) you added that is causing it to act up.
(Lab126's indexer program is worse than a spoiled child as far as behavior is concerned.)
Quote:
Originally Posted by Ffan
"The sensible way to check is to look at the output of htop, and check if the indexing thread is being silly. Checking the logs (showlog in a shell, ;dm in the search bar) is also generally a good idea."
And this sounds good but kinda stumps me. htop I heard before in regards to linux other than that I'm drawing a bit blank. Could you give me something a little more "step-by-step"-ish or at least point me in the direction to some basic instructions for this ? :P
|
One way:
With command line access, just run the program.
Usually that involves using either ssh or telnet over the USB cable -
both are included in the USBnet package.
Another way:
I don't recall that we have a KUAL button to capture the output of (h)top -bn1 as a "document".
But the Kindle Menu application will display a "task list" -
which may be enough to confirm it is the indexer gone dumb that is running down your battery.
- - - -
Strange Linux (or any *nix) terms encountered - -
All (should) have a related manual page.
Embedded systems (like the Kindles) do not have the manual documents installed.
AH -
But all the web search engines recognize the usage of the man(ual) command:
via google:
man htop
gives as first hit:
http://linux.die.net/man/1/htop
and other interesting hits, such as:
http://mylinuxbook.com/htop-interact...ocess-monitor/
- - - -
Student assignment:
man ssh
man telnet