[Zope-Checkins] CVS: Zope/doc - ENVIRONMENT.txt:1.10 LOGGING.txt:1.8

[Toby Dickenson]

Update of /cvs-repository/Zope/doc
In directory cvs.zope.org:/tmp/cvs-serv950/doc

Modified Files:
	ENVIRONMENT.txt LOGGING.txt 
Log Message:
merged from toby-syslog-access-branch

=== Zope/doc/ENVIRONMENT.txt 1.9 => 1.10 ===
 
         Setting this environment variable will cause Zope to try and write
-        to the named UNIX domain socket (usually '/dev/log').  This will
-        only work on UNIX.
+        the event log to the named UNIX domain socket (usually '/dev/log').
+        This will only work on UNIX.
 
         See also: LOGGING.txt
 
@@ -126,6 +126,13 @@
 
         See also: LOGGING.txt
 
+    ZSYSLOG_ACCESS="/dev/log"
+    ZSYSLOG_ACCESS_FACILITY="facilityname"
+    ZSYSLOG_ACCESS_SERVER="machine.name:port"
+
+        Like ZSYSLOG, ZSYSLOG_FACILITY, and ZSYSLOG_SERVER, but
+        controlling the sending of access information to syslog
+        (rather than controlling the sending of the event log)
 
     Z_DEBUG_MODE      "yes" or "no"
     BOBO_DEBUG_MODE   "yes" or "no"  (obsolete)


=== Zope/doc/LOGGING.txt 1.7 => 1.8 ===
    work on UNIX.
 
+   (In versions up to Zope 2.6, this also caused the access log
+   to be sent to syslog. In version 2.6 this is now controlled
+   by the separate ZSYSLOG_ACCESS environment variable)
+
   ZSYSLOG_FACILITY="facilityname"
 
    Setting this environment variable will cause Zope to use the
@@ -41,6 +45,11 @@
    'port' which must be an integer.  The default syslogd port is '514' 
    but Zope does not pick a sane default, you must specify a port.
    This may change, so check back here in future Zope releases.
+
+   (In versions up to Zope 2.6, this also caused the access log
+   to be sent to syslog. In version 2.6 this is now controlled
+   by the separate ZSYSLOG_ACCESS_SERVER environment variable)
+
 
 Calling the logger in your code