On 2007-05-21 18:16:00 -0400, Cristian Rodriguez R. wrote:
> Marcus Rueckert escribió:
> 
> > imho the problem is more general.
> 
> Yes, and I was unableto figure a better solution, that's the reason why
> I used that. ;)
> 
> > 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.
> 
> there is yet another issue with this approach, the "restart" must be
> done when the transaction finishes, if I install apache2-mod_php5 it may
> pull other PHP modules that really needs to be updated **before**
> restarting.

as we cant use rpm transactions (many installer install one rpm per rpm
call) we have to use some external script here. and each php module just
does %restart_on_update apache2 e.g. aswell. so they "trigger" a restart
of it aswell. [1]

> > which can be picked up by some SuSEconfig script in the end.  [1]
> 
> wasnt it deprecated ? ;)

i know we try to minimize the usage of it. you can always bring up a
better idea for the problem.;)

    darix

[1] Although this gets a bit tricky. who will restart my php fastcgi
    init script?;) do we want to have it in the distro at all?

-- 
           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]

Reply via email to