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 users should be aware of this. I have never see apache server showing log entries in a wrong order or delayed? Then why delay it in mod_jk?? By not flushing output immediatelly you are shirnking the functionality of logging mechanism. -- Radek 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 EMERG. > DEBUG and TRACE uses fflush so the order of messages can be traced, > but that is also dubious because the messages could come from > different threads, so the best would be to use the fflush only > with ERROR and EMERGE levels. > > Regards, > Mladen. > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > > --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
