[Zope-Checkins] CVS: Zope/lib/python/Controller - directives.csv:1.1.2.2

[Chris McDonough]

Update of /cvs-repository/Zope/lib/python/Controller
In directory cvs.zope.org:/tmp/cvs-serv7662

Modified Files:
      Tag: chrism-install-branch
	directives.csv 
Log Message:
Clean up some directive names and descriptions.


=== Zope/lib/python/Controller/directives.csv 1.1.2.1 => 1.1.2.2 ===
--- Zope/lib/python/Controller/directives.csv:1.1.2.1	Mon Aug 26 02:22:37 2002
+++ Zope/lib/python/Controller/directives.csv	Mon Aug 26 18:46:03 2002
@@ -1,7 +1,7 @@
 CATEGORY	DIRECTIVE	DESC	TYPE	VALTYPE	INFLUENCES	META_DEFAULT	DEFAULT	EXAMPLE
-general	instance_home	The path to the data files, local product files, import directory, and Extensions directory used by Zope.  One software_home can support many instance_homes.	env	path	INSTANCE_HOME	none (required)	None	/home/chrism/projects/sessions
-general	software_home	The path to the majority of the Python software files used by Zope.	env	path	SOFTWARE_HOME	none (required)	None	/home/chrism/software/Trunk/lib/python
-general	zope_home	The 'top-level' Zope software directory (home of the ZServer directory, the doc directory, the utilities directory, etc.)	env	path	ZOPE_HOME	none (required)	None	/home/chrism/software/Trunk
+general	zope_home	The 'top-level' Zope software directory (home of the Zserver directory, the doc directory, the utilities directory, etc.)	env	path	ZOPE_HOME	none (required)	None	/home/chrism/software/Trunk
+general	instance_home	The path to the data files, local product files, import directory, and Extensions directory used by Zope.	env	path	INSTANCE_HOME	none (required)	None	/home/chrism/projects/sessions
+general	software_home	The path to the majority of the Python software files used by Zope.  One software_home can support many instance_homes.	env	path	SOFTWARE_HOME	none (required)	None	/home/chrism/software/Trunk/lib/python
 general	client_home	The directory in which a running Zope's process identifier files are placed.	env	path	CLIENT_HOME	unset	None	/home/chrism/projects/sessions/var
 admin	debug_mode	If this directive is set to 'on', it causes the Zope process to not detach from the controlling terminal after it is run.  It also influences the behavior of some Zope objects at runtime (for example, when debug mode is "on", you are able to view changes made to DTMLFile and PageTemplateFile objects immediately; When it is 'off', you must restart the server to see the changes.  Setting this to 'off' when Zope is in a production environment is encouraged, as it speeds execution.	cmd	onoff	-D	on	None	on
 admin	effective_user	If you intend to run Zope as the "root" user, you must supply this directive with an effective username or userid number to which Zope will 'suid' after the server ports are bound.  This directive only works under UNIX and if Zope is started as the root user.	cmd	string	-u	unset	None	chrism
@@ -14,8 +14,8 @@
 log	acccess_syslog_facility	Same as 'event_syslog_facility', only for the "access" log data (z2.log data).	env	string	ZSYSLOG_ACCESS_FACILITY	unset	None	local7
 log	access_log_filename	The file path of the Zope 'access' log (z2.log) which is written in the combined logfile format.  The access log will be printed to standard output if the 'zserver_read_only' directive is set to 'on', regardless of this setting.	cmd	string	-I	INSTANCE_HOME/var/z2.log	None	/home/chrism/projects/sessions/z2.log
 log	access_syslog_path	Same as event_syslog_path, only for the "access" log data (z2.log data).	env	path	ZSYSLOG_ACCESS	unset	None	/dev/log
-log	access_syslog_server	Same as event_syslog_path, only for the 'access' data (z2.log data).	env	string	ZSYSLOG_ACCESS_SERVER	unset	None	Syslog.example.com:514
-log	event_log_file	Path to the Zope event log for debugging information.	env	path	EVENT_LOG_FILE	console	''	/home/chrism/projects/var/event.log
+log	access_syslog_server	Same as event_syslog_path, only for the 'access' data (z2.log data).	env	string	ZSYSLOG_ACCESS_SERVER	unset	None	syslog.example.com:514
+log	event_log_file	Path to the Zope event log for debugging information.	env	path	EVENT_LOG_FILE	unset	None	/home/chrism/projects/var/event.log
 log	event_log_severity	Filter events that can be written to the event log by priority.  A higher priority means fewer events will be written.  Choose one of (300, 200, 100, 0, -100, -200, or -300).  Descriptions of the integer levels are as follows: 300=PANIC, 200=ERROR, 100=WARNING, 0=INFO, -100=BLATHER, -200=DEBUG, -300=TRACE).	env	string	EVENT_LOG_SEVERITY	0	None	100
 log	event_syslog_facility	The facility used when the event log is being written to syslog (when 'event_syslog_path' or 'event_syslog_server' is set).	env	string	ZSYSLOG_FACILITY	user	None	local7
 log	event_syslog_path	Setting this directive will cause Zope to write the event log to syslog on the named UNIX domain socket on the local host.  This only works on UNIX.  It is overridden by specifying 'event_syslog_server'.	env	path	ZSYSLOG	unset	None	/dev/log
@@ -23,7 +23,7 @@
 log	trace_log_filename	The file path of the Zope 'trace' log which contains detailed request information which can later be interpreted by the requestprofiler.py script in the utilities directory. 	cmd	string	-M	unset	None	/home/chrism/projects/sessions/trace.log
 misc	default_structured_text_header_level	Set the default starting HTML header level for structured text documents.  The default is 3, which implies that  top-level headers will be created with an <H3> tag.	env	int	STX_DEFAULT_LEVEL	3	None	1
 misc	maximum_security_manager_stack_size	This variable allows you to customize the size of the Zope SecurityManager stack.  You shouldn't change this unless you know what it means.	env	int	Z_MAX_STACK_SIZE	100	None	200
-misc	publisher_profile_file	Causing this directive to point to a file on the filesystem will cause Zope's profiling capabilities to be enabled.  For more information, see the Debug -> Profiling tab of the Control_Panel.	env	path	PROFILE_PUBLISHER   unset	unset	None	/home/chrism/projects/sessions/var/profile/dat
+misc	publisher_profile_file	Causing this directive to point to a file on the filesystem will cause Zope's profiling capabilities to be enabled.  For more information, see the Debug -> Profiling tab of the Control_Panel.	env	path	PROFILE_PUBLISHER	unset	None	/home/chrism/projects/sessions/var/profile/dat
 misc	webdav_source_user_agents	Setting this directive enabls the retrieval of the *source* of Zope documents through the standard HTTP port instead of via a WebDAV source port (which are enabled via the 'webdav_source_server_ports' directive).   The value should be a regular expression that is matched against the user-agent string of the client.  Only clients which have a user-agent which match this regex will obain the source of the document via DAV on the normal HTTP port.	env	string	WEBDAV_SOURCE_PORT_CLIENTS	unset	None	cadaver.*
 network	dns_server_address	Specify the ip address of your DNS server in order to cause resolved hostnames to be written to Zope's access log.  By default, Zope will not resolve hostnames unless this is set.	cmd	string	-d	unset	None	127.0.0.1
 network	ip_address	The IP address on which Zope's various server protocol iimplementations will listen for requests.  If this is unset, Zope will listen on all IP addresses supported by the machine.	cmd	int	-a	unset	None	127.0.0.1