We have several modules which "exit(1)" from their post_config
hook if something bad happens that the administrator must correct
(e.g., mod_unique_id, mod_rewrite). But when they "exit(1)" cleanups
are't run. If post_config was RUN_ALL instead of RUN_VOID then such
modules could just return a failure code from their post_config and
main() could do the right thing (call destroy_and_exit_process()).
Any reason not to do this?
--
Jeff Trawick | [EMAIL PROTECTED] | PGP public key at web site:
http://www.geocities.com/SiliconValley/Park/9289/
Born in Roswell... married an alien...
