You are viewing a plain text version of this content. The canonical link for it is here.
Posted to bugs@httpd.apache.org by bu...@apache.org on 2005/07/17 03:16:36 UTC
DO NOT REPLY [Bug 35768] New: -
Missing file logs at far too high of log level
DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG�
RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT
<http://issues.apache.org/bugzilla/show_bug.cgi?id=35768>.
ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND�
INSERTED IN THE BUG DATABASE.
http://issues.apache.org/bugzilla/show_bug.cgi?id=35768
Summary: Missing file logs at far too high of log level
Product: Apache httpd-2.0
Version: 2.0.54
Platform: All
OS/Version: All
Status: NEW
Severity: trivial
Priority: P2
Component: Core
AssignedTo: bugs@httpd.apache.org
ReportedBy: tv@duh.org
APLOG_ERROR and APLOG_WARNING are used for some very important log messages, but
in order to squelch "file does not exist" log messages, the admin must set
LogLevel crit. This is suboptimal. A "file not found" type of condition is a
perfectly normal, if somewhat notable, operation of any Web server and should
not be logged at an error level on par with internal Web server problems.
I would suggest APLOG_NOTICE for these log messages (server/core.c), as that
preserves the obvious code intent of making these more notable conditions, but
moves the priority below messages that may require admin user intervention.
--
Configure bugmail: http://issues.apache.org/bugzilla/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.
---------------------------------------------------------------------
To unsubscribe, e-mail: bugs-unsubscribe@httpd.apache.org
For additional commands, e-mail: bugs-help@httpd.apache.org