thelonelycoder
Part of the Furniture
I just tested it on a 39 MB large file. It took 55 seconds to sort it on my RT-AC1900P. It would have to be a VERY large history file.1) It is possible - especially since we are preserving history that this file could grow very large. Therefore the sort feature could indeed peg CPU while it operates on a large file. How large this file has to be and how many CPU cycles it could take up are unknown to me, but this is what could be happening to some?
It's a minor issue, don't blow it up as if it nuked a router. Diversion is installed and it keeps the history file. I just keep the shell history commands, sort and remove duplicates. As a bonus to Diversion users.2) It would be nice if the preservation of the file wasn't linked to the sorting. Some people might like to have the file retained, but don't want it sorted for a couple of reasons:
- they have a large file and don't want the CPU cycles associated with it. (if indeed that is the cause of the observed issues some have).
- they want their history preserved as-is and don't want recent commands to just be put in randomly (based on sort order).
- possible concerns about excess write activity to jffs/flash memory. (I don't really know the true impact of this, but I know some users thing it is a big deal).
What feature, except for keeping the shell history do you think is unnecessary in Diversion?I've been seeing a lot of "feature creep" in ab-solution/Diversion's history. Lots of things that really have nothing (or very little) to do with the function of as-blocking seem to be integrated into the script.