*** empty log message ***

doc/DEBUGGING.txt

+
+Running Zope in Debug Mode
+
+  If you wish to run Zope in debug mode, use the -D command line
+  switch.  This will have the following effect::
+
+   o On UNIX, Zope will not detach from the controlling terminal.
+
+   o Zope will print logging information to standard error.
+
+   o The Z_DEBUG_MODE environment variable gets set, which causes some 
+     other cool stuff in Zope to happen.

doc/SECURITY.txt

+
+Setting the Zope "super manager" name and password
+
+  Because Zope is managed through the web, user names and passwords must be
+  used to assure that only authorized people can make changes to a Zope
+  installation.  User names and passwords are normally defined by creating
+  and modifying user folders within Zope.
+
+  A special "super manager" user name and password are defined outside
+  the application for two reasons
+ 
+    * Some user name and password are needed to enable creation of
+      initial normal managers of your Zope site.
+
+    * The "super manager" provides an all-powerful user that can do
+      anything in the application and whose password cannot be changed
+      through the application user interface.
+
+  This user name and password is defined in the 'access' file located
+  in the Zope directory. It should be readable only by the user
+  as which your web server runs.
+
+  The super manager username and password should only be used when
+  defining the normal management users and passwords and when dealing
+  with unusual situations, like lost (or hacked) manager user names and
+  passwords.
+
+  The access file should consist of a single line of the form:
+
+    name:password
+
+  The build scripts automatically create an 'access' file for you, 
+  using a default username and password of:
+
+    superuser:123
+
+  It is *highly recommended* that you change the default super manager 
+  name and password by editing your 'access' file after running the
+  build script. When you begin managing your Zope installation you
+  will need to enter the superuser name and password when prompted.
+
+  Note that you may also add an optional third component to the line
+  in the access file to restrict super manager access by domain. 
+  For example, the line:
+
+    mario:nintendoRules:*.mydomain.com
+ 
+  in your 'access' file will only allow super manager access to your 
+  installation from *.mydomain.com machines. Attempts to access the
+  system from other domains will fail, even if the correct superuser
+  name and password are used.
+
+Setting permissions on the var directory.
+
+  You need to set permissions on the Zope var directory.
+  Zope needs to read and write data from its var directory. Before
+  running Zope you should ensure that you give adequate permissions
+  to the Zope var directory for the userid Zope will run under.
+
+  Depending on how you choose to run Zope you will need to give
+  different permissions to the var directory.  If you use Zope with an
+  existing web server, it will probably run Zope as 'nobody'. In this
+  case 'nobody' needs read and write permissions to the var directory.
+
+  If you change the way you run Zope you may need to modify the permissions
+  of the var directory and the files in it to allow Zope to read and write
+  under its changed userid.