server/log.c discards anything higher than WARNING if the server_rec is NULL.

But, when adding new traceN messages deep down in modules,
request/conn/server recs might not be handy.

Is it safe to use extern server_rec* ap_server_conf in random modules
for trace messages?

Or should server/log.c know the difference between "still in startup"
and "stupid module couldn't find a server-rec to pass but really wants
info in main server errorlog via stderr?

(or, should server/log.c be willing to log anything < WARNING and >
TRACE1 to stderr via s==NULL? as long as it matches the LogLevel

-- 
Eric Covener
[email protected]

Reply via email to