jim         00/01/08 06:41:20

  Modified:    .        STATUS
  Log:
  Some updates. Before we release I'd like for us
  to look at these 2 additions. The HPUX problem I consider a
  show-stopper (it was before). Randy, can you confirm that
  the builds are broken?
  
  Revision  Changes    Path
  1.778     +16 -4     apache-1.3/STATUS
  
  Index: STATUS
  ===================================================================
  RCS file: /export/home/cvs/apache-1.3/STATUS,v
  retrieving revision 1.777
  retrieving revision 1.778
  diff -u -r1.777 -r1.778
  --- STATUS    2000/01/06 17:02:58     1.777
  +++ STATUS    2000/01/08 14:41:19     1.778
  @@ -1,5 +1,5 @@
     1.3 STATUS:
  -  Last modified at [$Date: 2000/01/06 17:02:58 $]
  +  Last modified at [$Date: 2000/01/08 14:41:19 $]
   
   Release:
   
  @@ -25,15 +25,27 @@
   
   RELEASE SHOWSTOPPERS:
   
  -
  -RELEASE NON-SHOWSTOPPERS BUT WOULD BE REAL NICE TO WRAP THESE UP:
  -
       * HPUX binary build failure due to the fact that it is building
         libstandard.a and adding .so objects to the libstandard.a starting
         with mod_vhost_alias.so.
           Message-ID: <[EMAIL PROTECTED]>
        Status: Randy committed a temporary fix
  +     UPDATE: Keith Wannamaker reports that Ralf's patch to
  +     fix PR4974 has broken this again. Please see:
  +       <[EMAIL PROTECTED]>
  +
  +RELEASE NON-SHOWSTOPPERS BUT WOULD BE REAL NICE TO WRAP THESE UP:
   
  +    * Cliff Woolley suggests the following patch to fix a problem
  +      with using mod_status and mod_vhost_alias. At issue is the
  +      fact that because mod_vhost_alias does not create actual
  +      vhost structures, the server-name reported in mod_status
  +      is incorrect. The patch reverts to the old behavior of
  +      storing the server-name of the request as a string in
  +      scoreboard.
  +        Message-ID: <[EMAIL PROTECTED]>
  +     Status: Jim -0
  +      
       * long pathnames with many components and no AllowOverride None
         Workaround is to define <Directory /> with AllowOverride None,
         which is something all sites should do in any case.
  
  
  

Reply via email to