I see, thanks for the explain.
On Fri, May 4, 2012 at 11:46 AM, Matthieu Tourne
<matthie...@gmail.com> wrote:
>
>
> On Thu, May 3, 2012 at 8:42 PM, agentzh <age...@gmail.com> wrote:
>>
>> On Fri, May 4, 2012 at 11:16 AM, wd <...@wdicc.com> wrote:
>> > I think it's something like a mmap? Not logs like the access_log or
>> > error_log.
>> >
>>
>> AFAIK, the log_by_lua* thing is a just "log-phase" handler. It does
>> not necessarily generate logs nor access shared memory storage. It
>> runs the same phase as the standard ngx_log module that usually
>> generates access logs.
>>
>
> This is correct, it doesn't generate logs per se.
>
> There is an example in the doc on how to aggregate simple values and output
> them using a content handler in another location.
>
> Don't hesitate to email me directly if you have questions, openresty users!
>
>>
>> Matthieu's patch effectively solves the following github issue:
>>
>> https://github.com/chaoslawful/lua-nginx-module/issues/51
>>
>> Best regards,
>> -agentzh
>
>
>