[Zodb-checkins] CVS: ZODB3/Doc - zdctl.txt:1.2

Fred L. Drake, Jr. fred@zope.com
Fri, 21 Feb 2003 13:00:26 -0500


Update of /cvs-repository/ZODB3/Doc
In directory cvs.zope.org:/tmp/cvs-serv21775

Modified Files:
	zdctl.txt 
Log Message:
- "sockname" is "socket-name" in the configuration schema
- typo: dcoumented --> documented


=== ZODB3/Doc/zdctl.txt 1.1 => 1.2 ===
--- ZODB3/Doc/zdctl.txt:1.1	Fri Jan 24 14:20:10 2003
+++ ZODB3/Doc/zdctl.txt	Fri Feb 21 13:00:25 2003
@@ -8,7 +8,7 @@
 Starting with Zope 2.7 and ZODB 3.2, Zope has a new way to configure
 and control server processes.  This file documents the new approach to
 server process management; the new approach to configuration is
-dcoumented elsewhere, although some examples will be given here.  We
+documented elsewhere, although some examples will be given here.  We
 use the ZEO server as a running example, although this isn't a
 complete manual for configuring or running ZEO.
 
@@ -167,14 +167,14 @@
     program       runzeo.py -a 9999 -f Data.fs
     daemon	  true
     directory     /tmp/zeohome
-    sockname      /tmp/zeohome/zdsock
+    socket-name   /tmp/zeohome/zdsock
   </runner>
 
 The "program" and "daemon" lines correspond to the -p and -d command
 line options discussed above.  The "directory" line is new.  It
 specifies a directory into which zdrun (but not zdctl!) chdirs.  The
 Data.fs filename passed to runzeo.py is interpreted relative to this
-directory.  Finally, the "sockname" line names the Unix domain socket
+directory.  Finally, the "socket-name" line names the Unix domain socket
 that is used for communication between zdctl and zdrun.  It defaults
 to zdsock in the current directory, a default you definitely want to
 override for production usage.