Package: zope2.7 Version: 2.7.4-0-0 Followup-For: Bug #293486
I faced the same dilemna regarding how to start up the ZEO server. I ended up creating a separate init script, more or less copy-pasted from the zope2.7 init script. My concern is about the place where the ZEO server is supposed to reside. I put it under /var/local/lib/zeo/, waiting to see what the Maintainer would come up with (my latest bet was /var/lib/zope2.7/zeo). I am not convinced that the ZEO server should be under /var/lib/zope2.7/instance, as I do not see it as a ZOPE instance - and I might be wrong when saying that. Anyway, the patch that is proposed in this report assumes that ZEO has been created in the same path as ZOPE instances. If it is going to be the official policy then it has to be documented - more than just assumed by the init script. Thanks -- System Information: Debian Release: 3.1 APT prefers testing APT policy: (500, 'testing') Architecture: i386 (i686) Kernel: Linux 2.6.10 Locale: LANG=C, LC_CTYPE=C (charmap=ANSI_X3.4-1968) Versions of packages zope2.7 depends on: ii adduser 3.59 Add and remove users and groups ii debconf 1.4.30.11 Debian configuration management sy ii dpkg 1.10.26 Package maintenance system for Deb ii libc6 2.3.2.ds1-20 GNU C Library: Shared libraries an ii python2.3 2.3.5-1 An interactive high-level object-o ii python2.3-xml 0.8.4-1 XML tools for Python (2.3.x) -- debconf information: zope/upgrade/2.7: * zope/tips/2.7: * zope/tips/standalone_install: * zope/instance_home/move: false * shared/zope/restart: end -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
