Tarek Ziadé wrote: > when creating a Zope 2 buildout, the scripts within the bin folder adds to > the sys.path all paths to all eggs. > > That's fine, but if I run zope as a service (eg for example a NT service) , > I might loose in some cases these paths.
How so? > Since this recipe builds zope.conf and can catch up with the list of eggs > folders to pass into sys.path I would like to suggest adding a `path` > directive for each egg when zope.conf is built. > > I can code this in a branch and submit it when it's ready. > > If it's a bad idea, I would like to know how you guys do run a buildout zope > as a NT service for example, > to get the path correctly set. Did you use the "bin\instance install" and "bin\instance start" commands on Windows (counterpart of remove and stop)? These will use the "parts\instance\bin\servicewrapper.py" script that was written to preserve the path when run as a service. The install/remove extra commands are only available on Windows and call the zopeservice.py internally for you. This was meant to make it as easy as possible to run Zope as a NT service. If something is not working feel free to add bugs or patches to the official tracker at https://bugs.launchpad.net/collective.buildout Hanno _______________________________________________ Product-Developers mailing list [email protected] http://lists.plone.org/mailman/listinfo/product-developers
