[CalendarServer-users] Controlling log level 9.0
Dirk-Willem van Gulik
dirkx at webweaving.org
Fri Jan 13 13:31:38 PST 2017
On 13 Jan 2017, at 17:10, Dirk-Willem van Gulik <dirkx at webweaving.org> wrote:
> How does one control the loglevel on 9.0:
>
> With:
>
> <!-- Log levels -->
> <key>DefaultLogLevel</key>
> <string>warn</string> <!-- debug, info, warn, error —>
>
> The log is still showing (after memcache purge & restart):
>
> 2017-01-13T16:07:53+0000 [twext.enterprise.adbapi2#debug] ConnectionPool: txn free 'jobqueue.workCheck': free=1, busy=0, waiting=0
>
> And secondly - can LogLevels be used to control this in a more grannular fashion ? I had hoped that
>
> <key>LogLevels</key>
> <dict>
> <key>twext.enterprise.adbapi2</key>
> <string>error</string>
> </dict>
>
> would do the trick - but no dice sofar.
I am starting to suspect that there is something funny with freebsd its import-ordering. So this may in fact be a *BSD issue rather than a calendarserver issue.
Dw.
More information about the calendarserver-users
mailing list