Skip to content
  1. Oct 24, 2006
    • Jim Jagielski's avatar
      Once SSLMutex allowed for the setting of both the · 55fcb2ed
      Jim Jagielski authored
      locking method and the lockfile location, I never
      liked how AcceptMutex was linked to LockFile. This
      seemed unnecessary. Much better to have AcceptMutex
      do both as well. Plus, now that we will likely see
      other modules require a "standard" way of setting
      mutexes, why not have Apache provide that as
      an API of sorts.
      
      Anyway, LockFile is now depreciated and AcceptMutex
      is now SSLMutex-like. We also provide a short
      function that "parses" out a mutex parameter
      and strips out the mechanism and lockfile location.
      AcceptMutex and SSLMutex is this capability.
      
      
      
      git-svn-id: https://svn.apache.org/repos/asf/httpd/httpd/trunk@467326 13f79535-47bb-0310-9956-ffa450edef68
      55fcb2ed
  2. Oct 23, 2006
  3. Oct 22, 2006
  4. Oct 14, 2006
  5. Oct 12, 2006
  6. Oct 11, 2006
  7. Oct 10, 2006
  8. Oct 03, 2006
  9. Oct 02, 2006
  10. Sep 27, 2006
  11. Sep 26, 2006
  12. Sep 16, 2006
  13. Sep 15, 2006
  14. Sep 10, 2006
  15. Sep 09, 2006
  16. Sep 06, 2006
  17. Sep 05, 2006
  18. Sep 04, 2006
  19. Aug 28, 2006
  20. Aug 24, 2006
  21. Aug 14, 2006
    • Chris Darroch's avatar
      Introduce a check_config phase between pre_config and open_logs, · e2725f04
      Chris Darroch authored
      to allow modules to review interdependent configuration directive
      values and adjust them while messages can still be logged to the
      console.
      
      The open_logs phase is already used somewhat for this purpose by
      certain MPMs (winnt, prefork, worker, and event) but only by forcing
      their functions ahead of the core ap_open_logs() function, and
      since this phase runs after the ap_signal_server function during startup,
      it can not be used to generate messages on the console when restarting.
      
      Add the check_config phase to mod_info and mod_example.
      
      Handle relevant MPM directives during this phase and format messages
      for both the console and the error log, as appropriate.  Bounds and sanity
      checks on the values of the MPM directives are handled in sequence in
      this phase instead of in the various directive handling functions, since
      those functions (e.g., set_max_clients()) may not be called at all if their
      directives do not appear in the configuration files...
      e2725f04