Hello everyone, I have been contemplating the package I have with respect to configuration, and the recent thread on -devel about a fortnight ago that "all packages use DebConf". The majority of separately packaged Apache modules use a very similar post installation script that handle checking if the module has been loaded in the user's httpd.conf (a listed conffile), and prompts the user to add it if it has not, as well as prompting to restart the Apache Server daemon. Up to now this has been an interactive question for each module. Hence, with 'N' module packages installed, you will be prompted to restart Apache (graceful restart) 'N' times. The loading and unloading of individual modules should probably be a separate question for each module, since a user may or may not want to activate a module on a case by case basis (despite having just installed it). DebConf-ing this question in the manner outlined in the documentation and example is reasonably straight forward. However the option of restarting Apache after a module is upgraded could perhaps be made common amongst all module packages being upgraded or installed in one session. Would this be a shared template in DebConf? My opionion here is we want to mini5imise the 'downtime' for the web site we are running, and performing N restarts because we have a new apache, new libapache-mod-ssl, new libapach-mod-perl, etc, seems a bit bothersome (but perhaps unavoidable?). Furthermore, how can we ensure that this shared question is actually asked every time, and not just the initial result saved and reused on every subsequent `apt-get upgrade`? By every time, I mean once every time one or more modules is upgraded, and no more than once? Anyway, a shove in the right direction on this topic would be much appreciated. Yours, James -- James Bromberger <james_AT_rcpt.to> www.james.rcpt.to Remainder moved to http://www.james.rcpt.to/james/sig.html
Attachment:
pgpkz7RdGaOO6.pgp
Description: PGP signature