Your message dated Sun, 16 Jul 2006 22:13:35 +0200
with message-id <[EMAIL PROTECTED]>
and subject line [Pkg-zope-developers] Bug#378364: zope-common: upgrades 
restart all instances, not just those in /etc/default/zope*
has caused the attached Bug report to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what I am
talking about this indicates a serious mail system misconfiguration
somewhere.  Please contact me immediately.)

Debian bug tracking system administrator
(administrator, Debian Bugs database)

--- Begin Message ---
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


--- End Message ---
--- Begin Message ---
Il giorno sab, 15/07/2006 alle 10.13 -0700, Ross Boylan ha scritto:
> 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"

/etc/default/zope3 does control only /etc/init.d/zope3 and not the
actions performed by the maintainer scripts, which use dzhandle
directly.

When a product is upgraded, dzhandle tries to restart all the instances
which are affected by the update **and** have "configuring" or "end"
restart policy. This means that if your instance is stopped, then
dzhandle tries to start it unless you use "manually" as restart policy.

Please, modify your /etc/zope3/sandbox/debian_policy setting
"Restart-Policy: manually": this will prevent the restart of your
instance on upgrade.

> 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 think this is not a bug, and you can disable this behaviour as
explained above. I'm closing the report, but feel free to re-open it if
you do not agree and/or have a better idea/implementation.

Thanks,

-- 
Fabio Tranchitella <[EMAIL PROTECTED]>                        .''`.
Proud Debian GNU/Linux developer, admin and user.            : :'  :
                                                             `. `'`
   http://people.debian.org/~kobold/                           `-
_____________________________________________________________________
1024D/7F961564, fpr 5465 6E69 E559 6466 BF3D 9F01 2BF8 EE2B 7F96 1564

Attachment: signature.asc
Description: Questa รจ una parte del messaggio firmata digitalmente


--- End Message ---

Reply via email to