Log message for revision 96835:
DEBUGGING
Changed:
U Zope/trunk/doc/DEBUGGING.txt
U Zope/trunk/doc/index.txt
-=-
Modified: Zope/trunk/doc/DEBUGGING.txt
===================================================================
--- Zope/trunk/doc/DEBUGGING.txt 2009-02-20 15:39:28 UTC (rev 96834)
+++ Zope/trunk/doc/DEBUGGING.txt 2009-02-20 15:45:12 UTC (rev 96835)
@@ -1,25 +1,27 @@
Running Zope in Debug Mode
+==========================
- If you wish to run Zope in debug mode, set the 'debug-mode'
- configuration file parameter to 'on' (this is the default). This
- will have the following effects::
+If you wish to run Zope in debug mode, set the 'debug-mode'
+configuration file parameter to 'on' (this is the default). This
+will have the following effects:
- o On UNIX, Zope will not detach from the controlling terminal.
+- On UNIX, Zope will not detach from the controlling terminal.
- o The Z_DEBUG_MODE environment variable gets set, which causes
- behavioral changes to Zope appropriate for software development.
- See the configuration file description of 'debug-mode' for more
- information.
+- The Z_DEBUG_MODE environment variable gets set, which causes
+ behavioral changes to Zope appropriate for software development.
+ See the configuration file description of 'debug-mode' for more
+ information.
Using 'zopectl debug'
+---------------------
- A utility known as 'zopectl' is installed into generated instance homes.
- You can use it to inspect a Zope instance's running state via an
- interactive Python interpreter by passing zopectl the 'debug' parameter
- on the command line. The 'top-level' Zope object (the root folder) will
- be bound to the name 'app' within the interpreter. You can then use
- normal Python method calls against app and use the Python interpreter
- normally to inspect results::
+A utility known as 'zopectl' is installed into generated instance homes.
+You can use it to inspect a Zope instance's running state via an
+interactive Python interpreter by passing zopectl the 'debug' parameter
+on the command line. The 'top-level' Zope object (the root folder) will
+be bound to the name 'app' within the interpreter. You can then use
+normal Python method calls against app and use the Python interpreter
+normally to inspect results::
[chr...@james Trunk]$ bin/zopectl debug
Starting debugger (the name "app" is bound to the top-level Zope object)
Modified: Zope/trunk/doc/index.txt
===================================================================
--- Zope/trunk/doc/index.txt 2009-02-20 15:39:28 UTC (rev 96834)
+++ Zope/trunk/doc/index.txt 2009-02-20 15:45:12 UTC (rev 96835)
@@ -16,6 +16,7 @@
ZOPE3.txt
SETUID.txt
SIGNALS.txt
+ DEBUGGING.txt
CREDITS.txt
Indices and tables
_______________________________________________
Zope-Checkins maillist - Zope-Checkins@zope.org
http://mail.zope.org/mailman/listinfo/zope-checkins
