On 2007-05-21 14:51:15 +0200, Michal Marek wrote:
> php5 in server:php currently has
>
> %preun -n apache2-mod_php5
>
> if [ "$1" = "0" ]
> then
> if [ -x /usr/sbin/a2enmod ]
> then
> if a2enmod -q php5; then
> a2dismod php5
> fi
> fi
> fi
>
> %postun -n apache2-mod_php5
> %restart_on_update apache2
>
> Is there some policy about this? I looked at other apache2 modules in
> the distro and these don't automatically restart apache and with the
> exception of mod_apparmor also don't enable the module, instead a README
> or the package description tells the user to do so. Also the security
> advisories for the modules say "Please close and restart all running
> instances of Apache after the update.".
>
> Is it time to handle this automatically, or should we revert the change
> in php?
imho the problem is more general.
lets say i upgrade apache + modules:
%postun in the apache package does:
%restart_on_update apache2
now the other modules will be installed.
that can already take your server offline. if the apache mmn changes the
old modules that are still installed wont be loaded in the newer apache.
on the other hand we dont want to restart apache after each module.
we already discussed some kind of trigger file for this problem a few
weeks ago.
so %restart_on_update would e.g. create
/var/run/suseconfig/restart-<servicename>
which can be picked up by some SuSEconfig script in the end. [1]
that way we could restart services after all modules have been upgraded.
of course this applies to e.g. postfix, jabberd2 and many other packages
aswell.
darix
[1] i dont want to discuss the usefulness of suseconfig here. atm it
looks like a reasonable way to me. unlike the already discussed
triggerd.
--
openSUSE - SUSE Linux is my linux
openSUSE is good for you
www.opensuse.org
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
