October 2002 - Zope-Dev

Why does Zope move the Error Type and Value and replace with (see above)
by Chris Withers 09 Oct '02

09 Oct '02

Mark Poole wrote: > (Object: standard_html_header) > KeyError: (see above) A frequent complaint is that people don't include the error type and value when reporting errors from Zope, they just include the traceback. Now, normal python tracebacks include both the error type and error value. Why does Zope make this not happen? cheers, Chris

3 6

Multiple entries in the Index menu ... (Zope 2.6.1 b1)
by Joachim Werner 09 Oct '02

09 Oct '02

Hello! I am getting multiple identical entries in the Add menu of the indexes page of my ZCatalogs with Zope 2.6.1 b1. Is it just me? Could be a minor bug with filtering the all_meta_types or filtered_meta_types ... Joachim

2 1

CallProfiler problem
by Andre Schubert 09 Oct '02

09 Oct '02

Hi all, I have a problem removing the CallProfiler product from my Zope. After removing the product-directory from /usr/share/zope/lib/python/Products I got the following error after a restart: 2002-10-09T13:19:05 PROBLEM(100) ZODB Could not import class 'CallProfiler' from module 'Products.CallProfiler.CallProfiler P.S.: I also have removed the CallProfiler from Control_Panel/Products Who can help me ? Thanks in advance

1 0

Re: [Zope] WISH LIST - idea of new, DTMLRelation object
by Jaroslav Lukesh 09 Oct '02

09 Oct '02

| Odesílatel: Tino Wildenhain <tino(a)wildenhain.de> | perhaps you want to use <dtml-with rootfolder> ...navigation.. </dtml-with> | | ? | | Rootfolder could be the object you want to be the root (of course) | or in case of ZopeRoot, you get it via REQUEST.PARENT[0] | | However, before beating the dead horse, you should consider | replacing your routine with a python script, which could | also use ZCatalog in place of ObjectValues() - this saves | Memory and time since not all Objects have to be activated. | | This approach would also help you to go the way from | DTML to ZPT which is recommended. | | Greetings Many thanks, I am blind. Sure, it is right solution. I'm very sorry for confusing. Regards JL.

1 0

WISH LIST - idea of new, DTMLRelation object
by Jaroslav Lukesh 09 Oct '02

09 Oct '02

Hi all, I have an idea of new Zope DTML object with specific things. Dear Zope developers, please take attention to following lines: Imagine folder structure as / /folder1 DTMLMethod DTMLDocument DTMLRelation image.gif /folder11 /folder111 /folder112 /folder12 /folder2 /folder21 All three DTML* contains same code: <dtml-in "objectValues('Folder')"> <dtml-var id><br> </dtml-in> <img scr="<dtml-var absolute_URL>/image.gif"> Imagine what is doing that DTML Document or DTML Method are called from inside of /folder11. DTML Document make bad, but still functional (due acquisition) link to image. But DTML Relation will still give that same output, independent from where you call it: folder11 folder12 <img src="http://domain/folder1/image.gif"> Output is still independend from where you calling that DTMLRelation and give you right URL paths (relative or basolute). I think that DTML Relation (or you can call it better) should be very usefull, for example: 1. for navigation structure when you want to have constant navigation buttons what are dynamically generated from folder structure that have strong changes in any folder names 2. for image menus, where it give right path to images folder instead of acquired images etc. (I now, you can specify path with <dtml-var BASE1>/images/image.gif) Many thanks for your kindly attention. If it have simple solution by standard DTML code, let me know that code, please. Best Regards J. Lukesh

2 1

[Fwd: [Zope-Coders] silly windows request]
by Chris McDonough 09 Oct '02

09 Oct '02

I should have sent this request here in the first place... but I didn't. ;-) -----Forwarded Message----- From: Chris McDonough <chrism(a)zope.com> To: zope-coders(a)zope.org Subject: [Zope-Coders] silly windows request Date: 08 Oct 2002 19:49:36 -0400 If anybody has Win98/ME (not NT, I have that) with VC++ installed, do you think you might be able to spare a second to do me a favor and do perform the following commands: cvs -d :ext:cvs.zope.org:/cvs-repository -d InstallBranch \ -r chrism-install-branch Zope cd InstallBranch vcvars32 configure nmake build nmake install c:\Zope\inst\make_instance.py .. answer questions .. answer c:\Inst to instance_home question c:\Inst\bin\zctl.py start It works ok on NT (or at least it did a couple of days ago ;-) but I have no 98 machines to test it out on though. TIA, - C _______________________________________________ Zope-Coders mailing list Zope-Coders(a)zope.org http://lists.zope.org/mailman/listinfo/zope-coders

1 1

ZEO cache instrumentation -- any takers?
by Guido van Rossum 08 Oct '02

08 Oct '02

A while ago I announced a new ZEO cache instrumentation feature, and asked if anyone was interested in enabling this instrumentation in their site. I got exactly zero responses... :-( I'd like to repeat the offer. From the instrumentation data, it is easy to determine the most effective cache size for your site (a tool to do this is part of the release). All you need to do is replace one file, ClientCache.py. Both ZEO 1 and ZEO 2 are supported. The instrumentation code does *not* use zLOG and causes very little overhead. It can create a large log file though (100 MB per day at one Zope Corp customer). Here's a copy of my original announement: >Subject: ZEO cache analysis tools prerelease >From: Guido van Rossum <guido(a)python.org> >To: zope-announce(a)zope.org >Date: Tue, 10 Sep 2002 17:02:41 -0400 * Do you want to know if your ZEO client cache is configured properly? * Are you using ZEO but you didn't know it had a client cache? * Do you want to contribute towards a better ZEO client cache design? If you answered yes at least once, read on! Jeremy is working on a new ZEO 2 release; the first beta was released two weeks ago. For that release I have written cache instrumentation code that lets you review the effectiveness of the ZEO client cache. There's also a version of the instrumented cache for ZEO 1. I don't plan to work on it more before the ZEO 2 release (unless I receive bug reports). All code is available *now* from the ZODB3 CVS tree: http://cvs.zope.org/ZODB3/. In addition to adding instrumentation, some bugs affecting performance but not correctness of the cache have been fixed in the instrumented cache code. The instrumentation is controlled by an environment variable so you can leave the new cache code in place after turning off the instrumentation. I'm inviting everyone who is running ZEO seriously to install the cache instrumentation code, run it for a while, and send me the resulting trace file. (The trace files contain no privacy-sensitive data, so you don't have to worry about revealing anything about your site.) The trace files will be used as input to a simulation of a new cache design. The only way to validate a cache design is to run experiments, and trace files are the most reliable way to run such experiments. The more trace files I receive the better. The larger they are the better (traces of several days of uninterrupted service are ideal). I've got the disk space to burn. I should mention that I'm confident that the instrumentated cache works correctly: we've been collecting traces without problems at a Zope Corp customer site since last Wednesday. To enable the cache instrumentation, you need to replace a single file in the ZEO package used by the Zope application, set an environment variable, and restart the Zope application. The file you need to replace is named ClientCache.py. Here are the URLs: For ZEO 1: http://cvs.zope.org/ZODB3/ZEO1/ClientCache.py?rev=HEAD For ZEO 2: http://cvs.zope.org/ZODB3/ZEO/ClientCache.py?rev=HEAD Make sure to get the file for the ZEO version you are using! Details about enabling the tracing can be found here: http://cvs.zope.org/ZODB3/ZEO/README.txt?rev=HEAD If you want to play with the statistics or simulation programs yourself, get stats.py and simul.py from the ZEO directory: http://cvs.zope.org/ZODB3/ZEO/ These work with trace files produced by either version of the instrumented cache code. Once you have one or more trace files for me, the best way to get it to me is probably to place a gzipped copy on an FTP or HTTP server from which I can download it and mail me the URL. As I said, these trace files contain no sensitive data. If you still prefer a different approach, email me and we'll figure something out. --Guido van Rossum (home page: http://www.python.org/~guido/)

10 23

Re: [ZODB-Dev] ZEO signal feature
by Toby Dickenson 07 Oct '02

07 Oct '02

On Sunday 06 Oct 2002 4:56 pm, Chris McDonough wrote: > > It's probably unavoidable that the log file is opened as root -- > > it's used to report "can't setuid()". :-) Thats what syslog is for. It is good security practice that a daemon should *never* have a writeable file descriptor for its log file. If it does, and the daemon is compromised, an attacker can trivially cover his tracks by removing the incriminating evidence from the log file. > Pidfiles too. Currently it is common practice for Zope's 'stop' scripts to be run as root. We cant allow the pid files to be written by non-root users, otherwise those users could trick root into killing an arbitrary process. > The only real > purpose to running as root is to be able to bind to low-numbered TCP > ports. IMO there are better solutions to the problems to which low-numbered ports are a common solution. Zope/ZSS never *needs* a low numbered port, and zope should never be started as root. (I have cc'ed zope-dev. I suggest we continue there, rather than zodb-dev)

4 6

zdaemon fix
by Guido van Rossum 07 Oct '02

07 Oct '02

We recently had an event at a customer site where a ZEO process was started with bogus arguments that kept spewing messages in the log file forever: the zdaemon module kept restarting the program, and the program kept failing (without logging a message!). I think we've all gone through this. Killing the rogue program is a bit of a pain because it dies before the pid file is written. I am thinking of a fairly simple change to zdaemon: if it finds that it is continuously respawning the program more than 10 times in 2 minutes, it assumes there is a fatal error, log a PANIC level message, and exit. (I took the criterion, but not the response from init(8).) Are there any concerns about checking this in? This would go into Zope 2.7 and ZODB 3.1, and could possibly be backported to 2.6 and 2.5. --Guido van Rossum (home page: http://www.python.org/~guido/)

3 3

Re: [Zope-dev] http://cvs.zope.org/Products/Scheduler vs Xron for cron-like functionality. Advice?
by Johan Carlsson [Torped] 06 Oct '02

06 Oct '02

> > The Xron product release is almost a year old, > > but Scheduler seems to be only available via CVS. > > Can anyone comment as to the maturity/stability > > of these products? Any advice would be much appreciated. > I can't vouch for either of the products you mentioned, but I've had > good luck with cron on linux teamed with wget :-) > There doesn't seem to be much support in Zope for use cases > where an action is not event driven, ie not a request/response pair. > *** Vaporware Follows*** > What *I* want, (but haven't written yet) is a product that can do > continuous low level scraping of legacy data sources and feed this > data into an RDBMS or the ZODB. A kind of "helper daemon". How > each instance is scheduled would be one of many adjustable per > instance config options :-) However, assuming that I do get around > to building this product, I don't know where on the scale between > ugly hack and elegant, reusable solution it will fall. This will also > determine whether you ever see it on "zope.org" :-) > Adam Hi All, I'm interested in starting to maintain Xron, if it has potential to be a stable products. From the code it doesn't seem to do any strange things, but I would like to know if anybody has experience of using it in a production environment, or any other experiences and that would recommend not using it in a production environment. The central feature I'm interested in is the ability to setup packing policies inside Zope. I know many people uses Cron or Scheduler but I like to have one platform independent solution and preferably inside the Zope process. Regards, Johan Carlsson

5 8