Although this was a feature request it is not part of 9.2.
There are no plans to introduce this feature into the WebAdmin. Although some admins like the idea of the feature, the reality is that is makes almost no difference in the majority of cases where it is used, while also creating a large number of other problems.
You may wish to try SXL categorization, which still is a cloud categorization but also includes a local cache so it is significantly less traffic and much faster than CFF (the normal cloud categorization from astaro).
You can use SXL by setting sc_local_sb$ back to none and then setting use_sxl_urid to 1 (or turning on Endpoint Web Control).
I just wanted to briefly explain why we are not planning on supporting local_db and recommending SXL instead. In the future the default will be to use SXL for everything.
Lets say you have a single user browsing foo.com and you are doing 10 HTTP requests a minute for that site, for 20 minutes. In CFF there is 200 lookups. In SXL there is 2 lookups. That is 1% of the lookups of CFF. In local db there are 0 lookups.
Lets say you have twenty users browsing foo.com, each doing 10 requests a minute for 20 minutes. In CFF there is 4,000 lookups. In SXL there is 2 lookups. That is .05% of the lookups of CFF. In local db there are 0 lookups.
So I agree that local db still has the least number of lookups. But SXL ain't that bad, and the more users the better the caching is. [:)]
You have to turn off the sc_local_db as well (=none).
There is nothing specific in the log that says it is working (though it is possible to turn on more verbose logging), but you shouldn't see any more cffs01.... checks every 10 minutes.
There is a way you can infer it though. If you look at http.log each request has a cattime="12345" in microseconds.
So if you get a cattime that is 39000 that is 39 milliseconds to do the categorization, which means it was a cloud lookup. If you get a cattime that is 200 it is less than a millisecond, it must be local cache. Basically 5-6 digit numbers are cloud and 2-3 digit numbers are local.
There are some websites (google is an unfortunate example) where caching is not possible, so every request will have a cattime > 20ms.
All the ***time= in the logs are new for 9.2 and will be very useful for debugging. This includes the categorization time, regardless of what categorizer was used.
