Ainsi parlait Jean-Michel Dault :
> > have is once the new apache-specific config file has been inserted in
> > /etc/httpd/conf.d, how to reload apache configuration correctly ?
> > JMD use the following for apache2 itself:
> > if [ -e /usr/sbin/ADVXctl ]; then /usr/sbin/ADVXctl update;fi
> > However, i don't see the need to test for /usr/sbin/ADVXctl presence, as
> > it is needed by package dependencies. Moreover, it is not to be done for
> > all post/postun, as simple upgrade doesn't need to reload change, only
> > first installation and removal.
>
> I check for the presence of ADVXctl since it was "AESctl" a long time
> ago, and you're not really forced to upgrade apache-conf from version to
> version, so in the past, we had error messages.
However, if it is actually AESctl, then %postun doesn't work at all... Using a
versioned dependency is more secure here.
> Post scripts for Apache are a major PITA. Doing a graceful restart is
> not recommended, since some combination of packages, like mod_jk or
> mod_bwshare, don't like it, and may leave zombie processes. The only
> 100% proof solution is to stop apache and start it again.
>
> But this creates a mess when you upgrade multiple modules, since it
> takes forever to stop and restart apache all the time.
It should be doable to queue reload/restart/whatever request, and to only do
it at the end of the rpm transaction, the same way as running ldconf after
installing multiple library packages.
--
Suppressive fires -- won't
-- Murphy's Military Laws n�3
