(re)starting of a daemon after package update

Reindl Harald h.reindl at thelounge.net
Thu Jun 21 21:01:16 UTC 2012

Am 21.06.2012 22:52, schrieb Michal Hlavinka:
> On 06/20/2012 02:37 PM, Reindl Harald wrote:
>> Am 20.06.2012 14:32, schrieb Björn Persson:
>>> Michal Hlavinka wrote:
>>>> Correct approach would be to save state before installation of new
>>>> version starts and start dovecot (if flag is set) after old version is
>>>> removed - that would mean %postun script. This does not seem to work on
>>>> reinstall (the same version is installed) - %postun script is not executed.
>>> Please also consider what happens when the new version of Dovecot requires a
>>> new version of some library. RPM will ensure that both packages are updated in
>>> the same transaction, but if I understand correctly it's not until %posttrans
>>> that you can be sure that the new library is in place.
> %postun is sufficient, but it's not executed on package reinstall
>> one reason more why the cuurent behavior re-starting services
>> on updates is simply wrong:
> You complained that service is restarted during update. Well, in this case, restart is not sufficient. We even have
> to be sure, the service is not running when there are both old and new files in place. Not restarting the service
> would be "simply wrong"

is is NOT simpy wrong

* i am the admin
* i decide the time when a service is restarted
* you have no clue what implication a restart of whatever
  service has in my environment
* so you should give me a way to disable the auto-restarts globally

currently i have to rebuild every single server-package to remove this

can you imagine the side-efefcts restarting mysqld while update
in a environment dbmail postfix, dovecot and depending services
heavily using mysql?

you can NOT
i can - it is a disaster

i am the onbe who is controlling the machine and konwing each configuartion
and service-dependency on my machine because i have configured the whole
stuff and i know what i am doing - update mysqld without restart the service
is painless, AFTER the update i start a script stopping all the services
in the 100% right order for MY setup and start them again

this means a downtime around 10 seconds wihtout a single error
in /var/log/maillog - dong the restart blindly on update means
a LOT of errors and warnings in maillog

so please do not tell me what is right or wrong in MY setup
give me the option to decide GLOBALLY withut rebuild packages
what is the best for MY environment!

-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 262 bytes
Desc: OpenPGP digital signature
URL: <http://lists.fedoraproject.org/pipermail/devel/attachments/20120621/ab4ce53b/attachment.sig>

More information about the devel mailing list