+1. As you pointed out, NetWare has been using the Unix version which does not
eat the \r's. So far we haven't seen any problems at all with this.
Brad
Brad Nicholes
Senior Software Engineer
Novell, Inc., the leading provider of Net business solutions
http://www.novell.com
>>> "William A. Row
At 02:11 PM 3/4/2003, Branko Čibej wrote:
>William A. Rowe, Jr. wrote:
>
>+1. Every other bit of apr_file_* code treats all files as pure binary
>already. This shouldn't be an exception. We shouldn't eat \r's until we
>have real translated streams, and even then, BINARY should be the
>default ('cau
William A. Rowe, Jr. wrote:
>Someone pointed out that we eat \r's in apr_file_gets() ... now if we
>respected the BINARY flag to open that might not be "as much" of
>a problem - but it's deeper than that...
>
>We also don't reassemble \r\n pairs in apr_file_puts() either, which
>means any file tha
I see the following...
configure.in:1470: warning: AC_TRY_RUN called without default
to allow cross compiling
Any clues? Serious? Can we adjust the volume if not?
Someone pointed out that we eat \r's in apr_file_gets() ... now if we
respected the BINARY flag to open that might not be "as much" of
a problem - but it's deeper than that...
We also don't reassemble \r\n pairs in apr_file_puts() either, which
means any file that goes while(apr_file_gets()) apr_f
Sorry,
I sent the following message to wrong ML. Please ignore it.
On Wed, 05 Mar 2003 00:17:01 +0900, [EMAIL PROTECTED]
wrote:
> Hi,
>
> I have question about rotatelogs process handling.
>
> When apache is logging with rotatelogs and rotatelogs
> process died (e.g. accidentaly killed by some
Hi,
I have question about rotatelogs process handling.
When apache is logging with rotatelogs and rotatelogs
process died (e.g. accidentaly killed by someone),
Apache-1.3 respawns rotatelogs process and keeps logging but
Apache-2.0 does nothing and does not output log anymore.
What I found is th
