Am 02.11.16 um 16:49 schrieb David Osborne:
I've spotted an issue that seems to have been introduced at some point between 4.99.10 & 4.99.11 (and still present in tip as of today). When logpartialtimes are enabled, the access log seems to be logging the runtime of the previous entry.
Dear David,
many thanks for the excellent bug report. the error sneaked in during the large commit [1] addressing the HTTP/1.2 pipelined requests and the entailed modified life-cycle management. This bug is now fixed on bitbucket, the partial times are like before.
-gPS: I've as noticed, that we have currently no time statistics about what happens after a requests (cleanups, server traces, etc.). We can't include such statistics in the access.log via logpartialtimes (since while writing the access log entry, we have no idea, how long this will take, cleanup is later), be we can include it in the server statistics (accessible via "ns_server stats", and therefore useful for munin etc.). Maybe, we should add this as well.
[1] https://bitbucket.org/naviserver/naviserver/commits/121f1aace338714a894ad1277e0781c2132f0d5f
------------------------------------------------------------------------------ Developer Access Program for Intel Xeon Phi Processors Access to Intel Xeon Phi processor-based developer platforms. With one year of Intel Parallel Studio XE. Training and support from Colfax. Order your platform today. http://sdm.link/xeonphi
_______________________________________________ naviserver-devel mailing list naviserver-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/naviserver-devel
