From: "Ryan Bloom" <[EMAIL PROTECTED]> Sent: Thursday, January 17, 2002 2:39 PM
> > wrowe 02/01/17 12:15:12 > > > > Modified: server main.c log.c > > include http_log.h http_main.h > > Log: > > Allow the user to get detailed debugging information without a full > > recompile [absolutely necessary on Win32 and other platforms that > > really don't support administrator-compilation.] > > > > -e level follows the LogLevel options. > > > > The only question, should -e override the compiled-in default for > > the creation of the server_rec? No strong feeling either way, > here. > > Huh? Why is this necessary? This is exactly the same as -C"LogLevel > debug", isn't it? Also, how is this different from just putting the > information in the config file? The best that I can see is this is > changing the log level for when the server is starting up, which seems > like a dubious reason for a new argument. What new information are we > getting out of this? -C"LogLevel" isn't handled until the config tree parsing (or else you could simply add LogLevel info at the _very_ beginning of the config file. However, that isn't what this patch solves. It allows detailed diagnostic messages (debug, info, notice) earlier in the startup than once we get to config tree parsing. Because binary end-users may not be able to rebuild with a define DEFAULT_LOGLEVEL, we never have the chance to trace early module initialization phases, and discover earlier problems. Bill
