calsettrace(1) causes much journal logging

We call calsettrace(1) whenever we want to get statistics on a query. We often forget to turn it back off, since the performance hit is not much.

This isn't really a problem except – when calsettrace is on, it triggers a massive amount of logging in journalctl, which is unnecessarily consuming disk and cluttering up the journal.

I propose we use calsettrace(2 or 3) to turn on journal logging with statistics. The function accepts an integer, so we ought to be able to make it not journal log unless a value > 1 is used.

I proposed 2 or 3 because 2 >1 gives us a unique number but alternatively, 3 could be used as a bitmask such that 1 = stats, 2 = logging and 3 = both.