On Wednesday 25 June 2003 10:28, Jean-Michel Dault wrote: > I think we would need a "cooker-server" mailing list, where we only > discuss Apache, Samba, LDAP and other server-specific issues.
I agree. More classification would be great. This has been previously discussed, IIRC. > 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. Well, we need to restart only when it is _really_ needed. I propose to adopt a conservative approach, to do a graceful if we are sure it won't cause trouble. We can use cooker to test if there is some problem when upgrading. > But this creates a mess when you upgrade multiple modules, since it > takes forever to stop and restart apache all the time. > > Another thing is php modules. Should they restart Apache? What if > people only use the php-cli or use apache but with php-cgi? How do we > handle that? what about having a script who handled that ? something like apache_php_restart;, that detect which version of php is installed, and, maybe, with a system to detect if the module requires to completely restart apache. -- Micka�l Scherer
