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. Dw.
On 13 Jan 2017, at 17:10, Dirk-Willem van Gulik <dirkx@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.
Am 13.01.2017 um 22:31 schrieb Dirk-Willem van Gulik <dirkx@webweaving.org>:
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.
I see this too on fbsd 10.3 and 11.0 . Would you care to open a PR here https://bugs.freebsd.org/bugzilla/enter_bug.cgi <https://bugs.freebsd.org/bugzilla/enter_bug.cgi> ? Axel --- PGP-Key:29E99DD6 ☀ computing @ chaos claudius
Axel Rau writes:
Am 13.01.2017 um 22:31 schrieb Dirk-Willem van Gulik <dirkx@webweaving.org>:
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.
I see this too on fbsd 10.3 and 11.0 . Would you care to open a PR here https://bugs.freebsd.org/bugzilla/enter_bug.cgi <https://bugs.freebsd.org/bugzilla/enter_bug.cgi> ?
I also experience this on FreeBSD but I haven't spent much time investigating. Joe
participants (3)
-
Axel Rau
-
Dirk-Willem van Gulik
-
Joe Malcolm