[Zope-Checkins] CVS: Zope/inst/skel/inst/in - zope.conf.in:1.1.2.9

[Chris McDonough]

Update of /cvs-repository/Zope/inst/skel/inst/in
In directory cvs.zope.org:/tmp/cvs-serv25196/skel/inst/in

Modified Files:
      Tag: chrism-install-branch
	zope.conf.in 
Log Message:
Checkpoint checkin for inst directory.


=== Zope/inst/skel/inst/in/zope.conf.in 1.1.2.8 => 1.1.2.9 ===
--- Zope/inst/skel/inst/in/zope.conf.in:1.1.2.8	Thu Jan  2 11:50:56 2003
+++ Zope/inst/skel/inst/in/zope.conf.in	Fri Jan  3 01:21:21 2003
@@ -616,47 +616,57 @@
 #     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 WARN. Level may be any of "CRITICAL",
+#     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 type of log "handler" (file, syslog, NT event log, etc) to be
-#     used for the log being defined. Each "handler" section must contain
-#     two arguments: "constructor"(a Python-style constructor for a log
-#     handler instance) and "formatter" (a Python-style constructor for a
-#     formatter instance).  XXX describe more and get rid of
-#     constructor/formatter stuff in favor of more detailed keys.
+#     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
+#     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
 #
 # Influences: zope.py configuration
 #
 # Default:
 #
 #     The access log will log to the file $CLIENT_HOME/Z2.log at level
-#     WARN, the event log will log to the file $CLIENT_HOME/event.log at
-#     level WARN, and the trace log will not be written anywhere.
+#     INFO, the event log will log to the file $CLIENT_HOME/event.log at
+#     level INFO, and the trace log will not be written anywhere.
 #
 # Examples:
 #
 # <logger event>
 #   level WARN
-#   <handler>
+#   <custom_handler>
 #     constructor zLOG.LogHandlers.FileHandler(filename="${instance_home}/var/event.log", mode="a+")
 #     formatter logging.Formatter(fmt="%(message)s", datefmt=None)
-#   </handler>
+#     level WARN
+#   </custom_handler>
 # </logger>
 #
 # <logger access>
 #   level WARN
-#   <handler>
-#     constructor zLOG.LogHandlers.FileHandler(filename=${instance_home}/var/access.log", mode="a+")
-#     formatter logging.Formatter(fmt="%(message)s", datefmt=None)
+#   <file_handler>
+#      file /home/chrism/logs/foobar.log
+#      format %(message)s
+#   </file_handler>
 # </logger>
 #
 # <logger trace>
 #   level WARN
-#   <handler>
-#     constructor zLOG.LogHandlers.FileHandler(filename=${instance_home}/var/trace.log", mode="a+")
-#     formatter logging.Formatter(fmt="%(message)s", datefmt=None)
-#   </handler>
+#   <syslog_handler>
+#     host localhost
+#     port 514
+#   </syslog_handler>
+#   <nteventlog_handler>
+#     appname Zope
+#   </nteventlog_handler>
 # </logger>