Hi guys,
Is there any limit of the size of a message log entry? How to control this ?
I did this:
ap_log_rerror(APLOG_MARK, APLOG_INFO, 0, f->r,
"%s", buffer);
And the buffer was truncated on the error log. I check the strlen of the buffer
and it was about 320K, and I got only
On Wed, Mar 13, 2013 at 6:01 AM, Hoang Vu Dang wrote:
> Hi guys,
>
> Is there any limit of the size of a message log entry? How to control this ?
>
> I did this:
>
> ap_log_rerror(APLOG_MARK, APLOG_INFO, 0, f->r,
> "%s", buffer);
>
> And the buffer was truncated on the error log. I
On Wed, Mar 13, 2013 at 6:16 AM, Eric Covener wrote:
> On Wed, Mar 13, 2013 at 6:01 AM, Hoang Vu Dang wrote:
>> Hi guys,
>>
>> Is there any limit of the size of a message log entry? How to control this ?
>>
>> I did this:
>>
>> ap_log_rerror(APLOG_MARK, APLOG_INFO, 0, f->r,
>> "%s
Yes I am sure I can't find other entries related to that request.
How to find whether I used PIPE_BUF and how to increase that BUF size ?
On Mar 13, 2013, at 11:16 AM, Eric Covener wrote:
> On Wed, Mar 13, 2013 at 6:01 AM, Hoang Vu Dang wrote:
>> Hi guys,
>>
>> Is there any limit of the size
I traced this into the Apache source code (ver 2.4.4). It looks like the
error message string is really limited by the size of 8KB.
This line is in server/log.c:1097
"
static void log_error_core(const char *file, int line, int module_index,
int level,
On Wed, Mar 13, 2013 at 04:40:50PM +0100, Hoang-Vu Dang wrote:
> I traced this into the Apache source code (ver 2.4.4). It looks like the
> error message string is really limited by the size of 8KB.
>
> This line is in server/log.c:1097
>
> "
> static void log_error_core(const char *file, int line
well, I do not buy the idea of security reasons, but I agree with your last
sentence that they do not see the need to make this a configurable option,
the error log does not need it.
regarding my purpose: mod_dumpio dumps data into the error log file in
chunks, I want to merge them if the message
