[Zope-Checkins] CVS: Zope/skel/etc - zope.conf.in:1.1.2.7

Fred L. Drake, Jr. fred@zope.com
Fri, 14 Feb 2003 16:36:01 -0500


Update of /cvs-repository/Zope/skel/etc
In directory cvs.zope.org:/tmp/cvs-serv9643

Modified Files:
      Tag: new-install-branch
	zope.conf.in 
Log Message:
- some updates the description of logging configuration (not enough)
- change the default level of information stored in the event log; the
  default should be verbose enough that a first-time user can see what
  gets written to that log


=== Zope/skel/etc/zope.conf.in 1.1.2.6 => 1.1.2.7 ===
--- Zope/skel/etc/zope.conf.in:1.1.2.6	Fri Feb 14 15:47:24 2003
+++ Zope/skel/etc/zope.conf.in	Fri Feb 14 16:35:59 2003
@@ -575,26 +575,26 @@
 # Directives: logger
 #
 # Description:
-#     This area should define one or more "logger" sections of the names
-#     "access", "event", and "trace". The "access" logger logs Zope server
-#     access. The "event" logger logs Zope event information. The "trace"
-#     logger logs detailed server request information (for debugging
-#     purposes only). Each logger section may contain a "level" name/value
-#     pair which indicates the level of logging detail to capture for this
-#     logger. The default level is INFO. Level may be any of "CRITICAL",
-#     'ERROR", WARN", "INFO", "DEBUG", and "ALL". Each logger section may
-#     additionally contain one or more "handler" sections which indicates
-#     a types of log "handlers" (file, syslog, NT event log, etc) to be
-#     used for the logger being defined. There are 7 types of handlers:
-#     file-handler, syslog-handler, nteventlog-handler, http-handler,
-#     smtp-handler, null-handler, and custom-handler.  Each handler
-#     type has its own set of allowable subkeys which define aspects
-#     of the handler.  All handler sections also allow for the
+#     This area should define one or more "logger" sections of the
+#     names "access", "event", and "trace".  The "access" logger logs
+#     Zope server access.  The "event" logger logs Zope event
+#     information.  The "trace" logger logs detailed server request
+#     information (for debugging purposes only).  Each logger section
+#     may contain a "level" name/value pair which indicates the level
+#     of logging detail to capture for this logger.  The default level
+#     is INFO.  Level may be any of "CRITICAL", 'ERROR", WARN", "INFO",
+#     "DEBUG", and "ALL".  Each logger section may additionally contain
+#     one or more "handler" sections which indicates a types of log
+#     "handlers" (file, syslog, NT event log, etc) to be used for the
+#     logger being defined.  There are 5 types of handlers: logfile,
+#     syslog, win32-eventlog, http-handler, email-notifier.  Each
+#     handler type has its own set of allowable subkeys which define
+#     aspects of the handler.  All handler sections also allow for the
 #     specification of a "format" (the log message format string), a
 #     "dateformat" (the log message format for date strings), and a
-#     "level", which has the same semantics of the overall logger level
-#     but overrides the logger's level for the handler it's defined upon.
-#     XXXX much more detail necessary here
+#     "level", which has the same semantics of the overall logger
+#     level but overrides the logger's level for the handler it's
+#     defined upon.  XXXX much more detail necessary here
 #
 # Influences: zope.py configuration
 #
@@ -611,7 +611,7 @@
   level all
   <logfile>
     path $INSTANCE_HOME/log/event.log
-    level warn
+    level info
   </logfile>
 </eventlog>