[Pkg-zope-developers] Bug#378364: zope-common: upgrades restart all instances, not just those in /etc/default/zope*

Ross Boylan RossBoylan at stanfordalumni.org
Sat Jul 15 17:13:19 UTC 2006


Package: zope-common
Version: 0.5.24
Severity: normal

When I upgrade, all zope instances are restarted, despite the fact
that (for example) my /etc/default/zope3 includes
  INSTANCES="upj"

This is really obvious, because I have a broken instance "sandbox" and
zope churns away constantly restarting it until I kill it or at
reaches its retry cutoff.

I believe I've seen this behavior with other versions of zope, though
the one with zope3 is the the one that just bit me.

I could swear I reported this earlier and it was (marked) fixed
earlier, but I see no sign of either in the bug reports I've
reviewed.  At any rate, the problem persists.

I'm reporting this against zope-common at a guess about which package
is responsible.  Please reassign if appropriate.

invoke-rc.d zope3 start/stop seems to operate only on the appropriate
instance, so this behavior seems specific to upgrading.

-- System Information:
Debian Release: testing/unstable
  APT prefers testing
  APT policy: (990, 'testing'), (990, 'stable'), (50, 'unstable')
Architecture: i386 (i686)
Shell:  /bin/sh linked to /bin/bash
Kernel: Linux 2.4.27advncdfs
Locale: LANG=en_US, LC_CTYPE=en_US (charmap=ISO-8859-1)

Versions of packages zope-common depends on:
ii  adduser                       3.87       Add and remove users and groups
ii  debconf [debconf-2.0]         1.5.2      Debian configuration management sy
ii  python2.4                     2.4.3-7    An interactive high-level object-o

zope-common recommends no packages.

-- debconf information:
  zope-common/remove-instance-without-data: abort
  zope-common/admin-automatic-password:
* shared/zope/restart: end
  zope-common/instance-http-port:
  zope-common/admin-user: admin
  zope-common/keep-data-on-purge: true




More information about the Pkg-zope-developers mailing list