Mailing-List: contact cvs-help@apr.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@apr.apache.org
Date: 9 Dec 2001 20:54:43 -0000
Message-ID: <20011209205443.50703.qmail@icarus.apache.org>
From: jerenkrantz@apache.org
To: apr-cvs@apache.org
Subject: cvs commit: apr STATUS

jerenkrantz    01/12/09 12:54:43

  Modified:    .        STATUS
  Log:
  And, you thought there wasn't going to be anything happening with this
  item (FreeBSD and threading support)?  Ha!
  
  Revision  Changes    Path
  1.74      +16 -1     apr/STATUS
  
  Index: STATUS
  ===================================================================
  RCS file: /home/cvs/apr/STATUS,v
  retrieving revision 1.73
  retrieving revision 1.74
  diff -u -r1.73 -r1.74
  --- STATUS	2001/12/05 16:54:23	1.73
  +++ STATUS	2001/12/09 20:54:42	1.74
  @@ -1,5 +1,5 @@
   APACHE PORTABLE RUNTIME (APR) LIBRARY STATUS:			-*-text-*-
  -Last modified at [$Date: 2001/12/05 16:54:23 $]
  +Last modified at [$Date: 2001/12/09 20:54:42 $]
   
   Release:
   
  @@ -243,6 +243,21 @@
         FreeBSD.
   
         MsgID: <20010828091959.D17570@ebuilt.com>
  +        Status: Justin has tracked down a FreeBSD kernel hacker 
  +                (alfred@freebsd.org) and we've isolated some issues
  +                within src/lib/libc_r/uthread/uthread_sendfile.c.  There
  +                are some problems in FreeBSD between libc_r and the
  +                kernel implementation of sendfile.  We've made some 
  +                progress (we now send the headers correctly, but we seem 
  +                to send the file twice now!).  At this point, we are unsure
  +                if we are seeing an APR bug or a FreeBSD bug.  Alfred has 
  +                requested some time to look at the sendfile(2) code with
  +                APR's test suite.  Justin has gained enough knowledge in
  +                his conversations that he may be able to continue this
  +                work if no feedback comes.
  +
  +                We have a preliminary patch at:
  +                  http://people.freebsd.org/~alfred/uthread_sf.diff
   
       * Currently it is difficult if not impossible to return a proper
         status code from a thread using apr_thread_exit(), since the