httpd-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Ralf S. Engelschall" <...@engelschall.com>
Subject LogLevel confusion...
Date Tue, 14 Apr 1998 12:12:34 GMT

Can someone explain me why I always get these nerving debug messages

| [Tue Apr 14 14:08:17 1998] [debug] mod_so.c(258): loaded module
| config_log_module
| [Tue Apr 14 14:08:17 1998] [debug] mod_so.c(258): loaded module mime_module
| [Tue Apr 14 14:08:17 1998] [debug] mod_so.c(258): loaded module
| negotiation_module
| [Tue Apr 14 14:08:17 1998] [debug] mod_so.c(258): loaded module
| autoindex_module
| [Tue Apr 14 14:08:17 1998] [debug] mod_so.c(258): loaded module dir_module
| [Tue Apr 14 14:08:17 1998] [debug] mod_so.c(258): loaded module userdir_module
| [Tue Apr 14 14:08:17 1998] [debug] mod_so.c(258): loaded module access_module
| [Tue Apr 14 14:08:17 1998] [debug] mod_so.c(258): loaded module
| setenvif_module

on server startup even when I put

| ErrorLog /tmp/apache/var/logs/error_log
| LogLevel emerg

in front of the LoadModule lines. Is this because of the multiple
configuration reading or did I missed something? The messages are generated by
a command handler from mod_so which does:

    ap_log_error(APLOG_MARK, APLOG_DEBUG|APLOG_NOERRNO, NULL,
        "loaded module %s", modname);

But why does this debug message displayed _always_ independend where the
LogLevel resides in httpd.conf and independend what argument is uses?

Or more simply: What can a user do to get rid of these nerving message except
removing the above line in the source of mod_so.c?

                                       Ralf S. Engelschall
                                       rse@engelschall.com
                                       www.engelschall.com

Mime
View raw message