[Zope-Checkins] CVS: ZODB3/ZEO - README.txt:1.4

Guido van Rossum guido@python.org
Thu, 21 Nov 2002 13:55:28 -0500


Update of /cvs-repository/ZODB3/ZEO
In directory cvs.zope.org:/tmp/cvs-serv31547

Modified Files:
	README.txt 
Log Message:
- Change the trace filename to include a hyphen and the storage name.


=== ZODB3/ZEO/README.txt 1.3 => 1.4 ===
--- ZODB3/ZEO/README.txt:1.3	Wed Sep 11 17:25:39 2002
+++ ZODB3/ZEO/README.txt	Thu Nov 21 13:55:27 2002
@@ -59,11 +59,13 @@
 ----------------------
 
 To enable cache tracing, set the environment variable ZEO_CACHE_TRACE
-to the name of a file to which the ZEO client process can write.  If
-the file doesn't exist, the ZEO will try to create it.  If there are
-problems with the file, a log message is written to the standard Zope
-log file.  To start or stop tracing, the ZEO client process (typically
-a Zope application server) must be restarted.
+to the name of a file to which the ZEO client process can write.  ZEO
+will append a hyphen and the storage name to the filename, to
+distinguish different storages.  If the file doesn't exist, the ZEO
+will try to create it.  If there are problems with the file, a log
+message is written to the standard Zope log file.  To start or stop
+tracing, the ZEO client process (typically a Zope application server)
+must be restarted.
 
 The trace file can grow pretty quickly; on a moderately loaded server,
 we observed it growing by 5 MB per hour.  The file consists of binary