Bug#718677: apache2.conf comment: Isn't LogLevel better explained as severity then number of messages?

To: submit@bugs.debian.org
Subject: Bug#718677: apache2.conf comment: Isn't LogLevel better explained as severity then number of messages?
From: Regid Ichira <regid23@nt1.in>
Date: Sun, 4 Aug 2013 11:11:18 +0300
Message-id: <[🔎] 20130804081118.GC5199@nt1.in>
Reply-to: Regid Ichira <regid23@nt1.in>, 718677@bugs.debian.org

Package:  apache2
Version:  2.4.6-2
Severity: minor
Tags:     patch
File:     /etc/apache2/apache2.conf

--- /etc/apache2/apache2.conf	2013-07-21 19:47:15.000000000 +0300
+++ apache2.conf	2013-08-04 04:09:18.000000000 +0300
@@ -128,7 +128,7 @@ HostnameLookups Off
 ErrorLog ${APACHE_LOG_DIR}/error.log
 
 #
-# LogLevel: Control the number of messages logged to the error_log.
+# LogLevel: Control the severity of events logged to the error_log.
 # Available values: trace8, ..., trace1, debug, info, notice, warn,
 # error, crit, alert, emerg.
 # It is also possible to configure the log level for particular modules, e.g.

Reply to:

Follow-Ups:
- Bug#718677: marked as done (apache2.conf comment: Isn't LogLevel better explained as severity then number of messages?)
  - From: owner@bugs.debian.org (Debian Bug Tracking System)

Prev by Date: Bug#718650: [apache2] Shipped ports.conf refers to old path for 000-default configuration
Next by Date: Processed: tagging 718677, tagging 718650
Previous by thread: Bug#718650: marked as done ([apache2] Shipped ports.conf refers to old path for 000-default configuration)
Next by thread: Bug#718677: marked as done (apache2.conf comment: Isn't LogLevel better explained as severity then number of messages?)
Index(es):
- Date
- Thread