reopen 378364 thanks Hi Ross,
Il giorno dom, 16/07/2006 alle 14.59 -0700, Ross Boylan ha scritto:
> > 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.
>
> The behavior continues to seem undesirable for me, and I see a number
> of problem areas:
> 1) upgrades respecting runlevel
> 2) upgrades respecting instance selection in /etc/default/
> 3) documentation.
>
> I may have misunderstood or missed something, however.
Restart behaviour on upgrades can't be unified with system start-up
behaviour: I have several zope instances which I can't restart untill
the week-end or holidays, and in this way I can upgrade the machine at
any day, and then plan the restart. Even if an instance is started at
boot-time, this doesn't mean it is useful for me if apt tries to restart
it on upgrade. Also, think about the product upgrades: Plone 2.0.2 ->
2.0.3 requires migration, and this is something which I would prefer to
do in a second moment for **a particular** instance.
So, about the bug: what about restarting instances only if it is already
running? In my opinion this is the best solution. Anyway, I'll add some
documentation about the restart-policy (even if my english is terrible).
Especially for this last point, any help is welcome.
Have a nice day,
--
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
signature.asc
Description: Questa รจ una parte del messaggio firmata digitalmente
