in an earlier Slip i wrote that i was successful with Zope-2.6.2b5 and python2.1. The reconstruction of this attempt failed until now. Now i have tried it again, with a "little" change in the start-script. I started without any arguments like so: exec $PYTHON \ $PYTHONHOME1/z2.py \ -u zope -d [nameserver-ip] "$@" and the z2 Startup exception disappeared. The "cannot import Splitter" is now reflected in some ERROR(200). Successively i added my arguments and looked for the startup behaviour. The "-D" lets the startup end in an "z2 Startup exception". Finally startline is now: exec $PYTHON \ $PYTHONHOME1/z2.py \ -X -t 10 -u zope -d [nameserver-ip] "$@" Error producing startline: exec $PYTHON \ $PYTHONHOME1/z2.py \ -D -X -t 10 -u zope -d [nameserver-ip] "$@" strange, isn't it? Ralph -----Ursprüngliche Nachricht----- Von: Jamie Heilman [mailto:jamie@audible.transient.net] Gesendet: Mittwoch, 24. September 2003 09:49 An: Arenz, Ralph Betreff: Re: GNU tar damage for the 5000th time, was Re: [Zope] z2 startup exception Arenz, Ralph wrote:

i have read about issue #181 in the bug-list of zope.org. Obviously different people have found different workaorounds but that bug is not fixed yet!?

Well the bug is probably fixed, but once the damage has been done, its been done, and you're stuck with no option but to clean up the mess it leaves.

I have tried the attempt in bug-list entry #5, but this doesn't work.

Adding that import statement to the module __init__.py didn't let your Zope start? In that case you'd better ask the list for more help, I'm not a good person to ask about catalog/vocabulary hacking as I don't use them enough. -- Jamie Heilman http://audible.transient.net/~jamie/ "Paranoia is a disease unto itself, and may I add, the person standing next to you may not be who they appear to be, so take precaution." -Sathington Willoughby