Skip to content
Projects
Groups
Snippets
Help
Loading...
Help
Support
Keyboard shortcuts
?
Submit feedback
Contribute to GitLab
Sign in / Register
Toggle navigation
Z
Zope
Project overview
Project overview
Details
Activity
Releases
Repository
Repository
Files
Commits
Branches
Tags
Contributors
Graph
Compare
Issues
0
Issues
0
List
Boards
Labels
Milestones
Merge Requests
0
Merge Requests
0
Analytics
Analytics
Repository
Value Stream
Wiki
Wiki
Snippets
Snippets
Members
Members
Collapse sidebar
Close sidebar
Activity
Graph
Create a new issue
Commits
Issue Boards
Open sidebar
Kirill Smelkov
Zope
Commits
57cc29a5
Commit
57cc29a5
authored
Jul 21, 2003
by
Chris McDonough
Browse files
Options
Browse Files
Download
Email Patches
Plain Diff
Update for 2.7.
parent
0d230940
Changes
1
Hide whitespace changes
Inline
Side-by-side
Showing
1 changed file
with
32 additions
and
9 deletions
+32
-9
doc/DEBUGGING.txt
doc/DEBUGGING.txt
+32
-9
No files found.
doc/DEBUGGING.txt
View file @
57cc29a5
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 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.
o Zope will print logging information to standard error.
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.
o The Z_DEBUG_MODE environment variable gets set, which causes some
other cool stuff to happen in Zope.
Using 'zopectl debug'
In Zopes 2.7 and better, 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::
[chrism@james Trunk]$ bin/zopectl debug
Starting debugger (the name "app" is bound to the top-level Zope object)
>>> app.objectIds()
['acl_users', 'Control_Panel', 'temp_folder', 'browser_id_manager', 'session _data_manager', 'error_log', 'index_html', 'standard_error_message', 'standa rd_html_footer', 'standard_html_header', 'standard_template.pt']
>>>
Using the Medusa Monitor
If you're running ZServer with a medusa monitor port, you can
connect and interact via a python prompt with a running Zope
session, while others interact with it over the web.
NOTE: as of Zope 2.7, the Medusa monitor client is known to have
operational problems due to lack of maintenance. It may work, it
may not. If it doesn't work as advertised, please try 'zopectl
debug' instead.
If you're running Zope with a medusa monitor port, you can connect
and interact via a python prompt with a running Zope session, while
others interact with it over the web.
Some constraints:
...
...
@@ -29,7 +52,7 @@ Using the Medusa Monitor
To use the monitor, start it from the shell prompt like so (as if
from the Zope root):
python ZServer/medusa/monitor_client.py localhost 8099
python
lib/python/
ZServer/medusa/monitor_client.py localhost 8099
You'll get back a python prompt. To connect with the running Zope
session:
...
...
Write
Preview
Markdown
is supported
0%
Try again
or
attach a new file
Attach a file
Cancel
You are about to add
0
people
to the discussion. Proceed with caution.
Finish editing this message first!
Cancel
Please
register
or
sign in
to comment