Re: cvs commit: apache-1.3/src/main http_main.c

["William A. Rowe, Jr." <wr...@rowe-clan.net>]

At 10:58 AM 3/13/2002, you wrote:
>bnicholes    02/03/13 07:58:40
>
>   Modified:    src/main http_main.c
>   Log:
>   Added the -e command line directive for NetWare to force all fatal
>   configuration file errors to the logger screen rather than to the Apache
>   screen.  This allows Apache to shutdown cleanly and completely on an
>   error condition without losing the error information that was written 
> to the
>   screen or requiring user interaction to close the Apache screen.

Outch... this didn't penetrate my thick skull.

I'd introduced two new Apache 2.0 directives

   -e level  ---  specific warning level for messages prior to parsing 
LogLevel, e.g. -e debug

   -E tmpfile  ---  specify initial error log file [for services and things 
with no console]

These flags rather conflict with the new Netware -e Flag...

Can we come up with some comprimize on flags so that 1.3 and 2.0 don't
start drifting?  Unfortunately, both 2.0.36 and 1.3.24 introduced the two 
different \
meanings already.

In terms of the new Netware -e meaning, it sure sounds like that feature aught
to be a default behavior, no?  It really sounds sorta of similar to either 
syslog
logging on Unix or Event logging on NT.

Bill

Re: cvs commit: apache-1.3/src/main http_main.c

["William A. Rowe, Jr." <wr...@rowe-clan.net>]

At 11:21 PM 6/4/2002, William A. Rowe, Jr. wrote:
>At 10:58 AM 3/13/2002, you wrote:
>>bnicholes    02/03/13 07:58:40
>>
>>   Modified:    src/main http_main.c
>>   Log:
>>   Added the -e command line directive for NetWare to force all fatal
>>   configuration file errors to the logger screen rather than to the Apache
>>   screen.  This allows Apache to shutdown cleanly and completely on an
>>   error condition without losing the error information that was written 
>> to the
>>   screen or requiring user interaction to close the Apache screen.
>
>Can we come up with some comprimize on flags so that 1.3 and 2.0 don't
>start drifting?  Unfortunately, both 2.0.36 and 1.3.24 introduced the two 
>different \
>meanings already.
>
>In terms of the new Netware -e meaning, it sure sounds like that feature aught
>to be a default behavior, no?  It really sounds sorta of similar to either 
>syslog
>logging on Unix or Event logging on NT.

To be more specific, -e sounds very much like the converse of the -w option
on windows, which causes the window to remain open if an error is encountered
at startup [preventing the window from being closed before the message
can be read at the console.]