httpd-cvs mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From r..@apache.org
Subject cvs commit: httpd-2.0 STATUS
Date Tue, 23 Jul 2002 17:44:56 GMT
rbb         2002/07/23 10:44:56

  Modified:    .        STATUS
  Log:
  After an install, the default config files are useful.  After an upgrade
  they aren't.
  
  If the config directive's syntax changed, Apache will tell
  you which one changed, and the docs are a better place to go for details
  then the default config files.  BTW, the syntax of a directive hasn't
  changed for a VERY long time.
  
  If the semantics changed, then nobody will ever know that they need to
  look in the default config files to determine that they semantics changed,
  because there is no error message.
  
  The argument that you want to be able to get the defaults back doesn't
  hold water, because 99.9% of all admins backup their files before
  modifying them.  If you aren't backing them up, then that is your problem.
  
  The argument that you may not have a full config directory also doesn't
  hold water, because the assumption is that the conf/ directory is coming
  from a working server.
  
  Revision  Changes    Path
  1.704     +5 -1      httpd-2.0/STATUS
  
  Index: STATUS
  ===================================================================
  RCS file: /home/cvs/httpd-2.0/STATUS,v
  retrieving revision 1.703
  retrieving revision 1.704
  diff -u -r1.703 -r1.704
  --- STATUS	23 Jul 2002 17:24:35 -0000	1.703
  +++ STATUS	23 Jul 2002 17:44:55 -0000	1.704
  @@ -76,6 +76,10 @@
            sysconfdir/examples or manualdir/exampleconf/
            +1:   slive
   
  +      d) Installing a set of default config files when upgrading a server
  +         doesn't make ANY sense at all.
  +	 +1:   rbb
  +
       * apachectl should revert to just being an init script and
         httpd.sh should be the wrapper for httpd which sources envvars
         and allows any options to be passed through
  
  
  

Mime
View raw message