On Mon, 5 Mar 2001 06:56:37 -0800 (PST), [EMAIL PROTECTED] wrote:
>> No need, I've think I've got to the bottom of it now. It appears that the
>> OS/2 implementation of writev() chokes if the total bytes > 64k. It returns
>> EINVAL but server/core.c:3189 says /* XXX: log the error */ rather than
>> actually logging the error :-(
>
>Cool.
>
>> So what's a reliable way to ensure no more than 64k gets writev()'d? I
>> guess I should break it up appropriately in apr_sendv() as it's most likely
>> an OS/2 only problem.
>
>Could you do it in core_output_filter? We should NEVER be writing that
>much one time anyway, so putting it in the core should help us see it,
>along with a debug message about writing too much?
Well I noticed that the content length filter set aside ALL of
mod_include's output. I guess that's why core_output_filter got hit with it
all at once.
--
______________________________________________________________________________
| Brian Havard | "He is not the messiah! |
| [EMAIL PROTECTED] | He's a very naughty boy!" - Life of Brian |
------------------------------------------------------------------------------
