Jens Vagelpohl <jens@digicool.com> writes:
terry,
you forgot the step of actually connecting to the monitor :) there is a very short howto on using the correct client program to log into the monitor at:
http://www.zope.org/Members/teyc/howtoMonitorClient
and similar info at:
I don't use the monitor anymore, I just mount the database from a Python prompt: lefty /usr/local/zope/2.2.0/lib/python= python Python 1.5.2 (#1, Sep 17 1999, 20:15:36) [GCC egcs-2.91.66 19990314/Linux (egcs- on linux-i386 Copyright 1991-1995 Stichting Mathematisch Centrum, Amsterdam
import ZServer, Zope app = Zope.app() dir(app) ['Control_Panel', 'QuickStart', '__allow_groups__', '_objects', '_product_ac_permissions', '_product_meta_types', '_product_permissions', '_product_zclasses', 'acl_users', 'apps', 'bookmarks', 'breadcrumbs', 'index_html', 'standard_error_message', 'standard_html_footer', 'standard_html_header', 'tmp']
I'm not sure what the usefulness of the monitor is these days. I always run ZEO, so I don't have to stop publishing to connect to the database from the prompt. Does the monitor give you something that interactive python doesn't? I do know that python in a shell is more robust than the monitor was - the monitor used to crash when dumping lots of info, like printing a large dictionary. -- Karl Anderson karl@digicool.com