Hi,
the problem is not only a delay but also an order of the messages. I
think all messages should be flushed to the file as soon as they come.
When I choosing to log 'info' messages I accept the fact that it will
slow down the processing of requests. That is always a drawback of
logging. The use
Mladen Turk wrote:
Jean-frederic Clere wrote:
Radek Wierzbicki wrote:
Hello,
better :
if (l->level < JK_LOG_INFO_LEVEL || level==JK_LOG_EMERG ||
level==JK_LOG_ERROR)
No?
Flush should not be executed for INFO level. It slows the things
down by the factor of 2. I agree for ERROR and EM
Jean-frederic Clere wrote:
Radek Wierzbicki wrote:
Hello,
better :
if (l->level < JK_LOG_INFO_LEVEL || level==JK_LOG_EMERG ||
level==JK_LOG_ERROR)
No?
Flush should not be executed for INFO level. It slows the things
down by the factor of 2. I agree for ERROR and EMERG.
DEBUG and TRACE u
Radek Wierzbicki wrote:
Hello,
I see a problem with logging mechanism in mod_jk 1.2.14.1. The logger
buffers and delays the output of messages with levels below 'info'
(info, warning, error, emergency, request).
With the new version, setting the log level to 'error' on production
setups wi
