merged from toby-syslog-access-branch

doc/ENVIRONMENT.txt

@@ -100,8 +100,8 @@ Debugging and Logging
     ZSYSLOG="/dev/log"
 
         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 @@ Debugging and Logging
 
         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)

doc/LOGGING.txt

@@ -27,6 +27,10 @@ Zope Logging
    to the named UNIX domain socket (usually '/dev/log').  This will only 
    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
@@ -42,6 +46,11 @@ Zope Logging
    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
 
  If you want your own Zope extensions to use logging: