kernol
Very Senior Member
Not sure why you are getting stats from unbound like that. I am always around 91%.
Hi @juched - thanks for that. My prior installs of unbound had all been back in the days when the now so called "advanced" install option was readily available [it cleverly remembered your choice of "adv" or "advanced" as a preferred menu option].
A clean install from amtm Menu item 7 - now takes you down the "Easy" automated setup mode. I know one can still get to the advanced menu - but from terminal command prompt only. I followed the Easy auto install ... and encountered the low cache hits as per my original post.
I have now uninstalled unbound [nice job - much cleaner uninstall than before] and this time, immediately after amtm option 7 took "e" for exit without installing unbound_manager - and instead did an "advanced" install from the command prompt. I'm not a code digger - but that process seemed to me to have more functionality that the "Easy" mode ... and for eg - noticed the cache.txt routine flash up briefly [auto save and restore cache entries].
I will continue to monitor and report if need be.
I see you are a coder - so up to you [if you wish] to check if there is any difference from a cache persepective in the coding between Easy and Advanced routines. Just trying to be helpful .