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
6198897b
Commit
6198897b
authored
Jul 23, 1999
by
Ken Manheimer
Browse files
Options
Browse Files
Download
Email Patches
Plain Diff
Added info about medusa monitor.
parent
ac524674
Changes
1
Show whitespace changes
Inline
Side-by-side
Showing
1 changed file
with
41 additions
and
0 deletions
+41
-0
doc/DEBUGGING.txt
doc/DEBUGGING.txt
+41
-0
No files found.
doc/DEBUGGING.txt
View file @
6198897b
...
...
@@ -10,3 +10,44 @@ Running Zope in Debug Mode
o The Z_DEBUG_MODE environment variable gets set, which causes some
other cool stuff in Zope to happen.
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.
Some constraints:
o You must connect to a server running on the local host.
o You must authenticate as superuser.
o At the time of writing the superuser password (in the access
file) must be plain text, not encrypted. This should be
rectified by full 2.0 release.
To use the monitor, start it from the shell prompt like so (as if
from the Zope root; must be python 1.5.2 or later):
python ZServer/medusa/monitor_client.py localhost 8099
You'll get back a python prompt. To connect with the running Zope
session:
>>> import Zope
>>> app = Zope.app()
>>> dir(app.Control_Panel.Products)
['ExternalMethod', 'MIMETools', 'MailHost', 'OFSP', 'ZCatalog',
'ZGadflyDA', 'ZSQLMethods', '_objects']
>>>
To see ODB changes effected via the web since you got the app, you
may have to do a bit of magic:
>>> app._p_jar.sync()
To commit changes you make, before exiting, you may have to do
another bit of magic:
>>> get_transaction().commit()
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