httpd-cvs mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From dgau...@hyperreal.org
Subject cvs commit: apache-1.3/src/main http_main.c
Date Sat, 14 Feb 1998 12:40:31 GMT
dgaudet     98/02/14 04:40:31

  Modified:    src      CHANGES
               src/main http_main.c
  Log:
  note a few more PRs
  
  Revision  Changes    Path
  1.632     +2 -2      apache-1.3/src/CHANGES
  
  Index: CHANGES
  ===================================================================
  RCS file: /export/home/cvs/apache-1.3/src/CHANGES,v
  retrieving revision 1.631
  retrieving revision 1.632
  diff -u -r1.631 -r1.632
  --- CHANGES	1998/02/14 12:17:26	1.631
  +++ CHANGES	1998/02/14 12:40:24	1.632
  @@ -5,7 +5,7 @@
        or library bugs occasionally, and result in log spammage and
        a generally bad scene.  Now the child exits immediately,
        which seems to be a good workaround.
  -     [Dean Gaudet] PR#1747, 1107, 588, 1787
  +     [Dean Gaudet] PR#1747, 1107, 588, 1787, 987, 588
   
     *) Cleaned up some race conditions in unix child_main during
        initialization. [Dean Gaudet]
  @@ -763,7 +763,7 @@
   
     *) Work around problem under Linux where a child will start looping
        reporting a select error over and over.
  -     [Rick Franchuk <rickf@transpect.net>] PR#1107
  +     [Rick Franchuk <rickf@transpect.net>] PR#1107, 987, 588
   
     *) Fixed error in proxy_util.c when looping through multiple host IP
        addresses. [Lars Eilebrecht] PR#974
  
  
  
  1.290     +2 -1      apache-1.3/src/main/http_main.c
  
  Index: http_main.c
  ===================================================================
  RCS file: /export/home/cvs/apache-1.3/src/main/http_main.c,v
  retrieving revision 1.289
  retrieving revision 1.290
  diff -u -r1.289 -r1.290
  --- http_main.c	1998/02/14 12:17:28	1.289
  +++ http_main.c	1998/02/14 12:40:27	1.290
  @@ -3097,7 +3097,8 @@
   		     * and other boxes that implement tcp sockets in
   		     * userland (i.e. on top of STREAMS).  On these
   		     * systems, EPROTO can actually result in a fatal
  -		     * loop.  But we don't deal with that.
  +		     * loop.  See PR#981 for example.  It's hard to
  +		     * handle both uses of EPROTO.
   		     */
                   case EPROTO:
   #endif
  
  
  

Mime
View raw message