apr-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From r..@apache.org
Subject cvs commit: apr STATUS
Date Tue, 16 Mar 2004 02:23:33 GMT
rbb         2004/03/15 18:23:33

  Modified:    .        STATUS
  Log:
  Add a note about the problems with the locking API.  This is a showstopper,
  because it keep people from being able to create a portable program that
  uses cross-process locks.
  
  Revision  Changes    Path
  1.196     +11 -1     apr/STATUS
  
  Index: STATUS
  ===================================================================
  RCS file: /home/cvs/apr/STATUS,v
  retrieving revision 1.195
  retrieving revision 1.196
  diff -u -r1.195 -r1.196
  --- STATUS	21 Nov 2003 10:42:03 -0000	1.195
  +++ STATUS	16 Mar 2004 02:23:33 -0000	1.196
  @@ -25,6 +25,16 @@
   
   RELEASE 1.0 SHOWSTOPPERS:
   
  +    * apr_global_mutex_child_init and apr_proc_mutex_child_init aren't
  +      portable.  There are a variety of problems with the locking API when it
  +      is used with apr_create_proc instead of apr_fork.  First, _child_init
  +      doesn't take a lockmech_e parameter so it causes a segfault after the
  +      apr_proc_create, because the proc_mutex field hasn't been initialized.
  +      When the lockmech_e parameter is added, it _still_ doesn't work, because
  +      some lock mechanisms expect to inherit from the parent process.  For
  +      example, sys V semaphores don't have a file to open, so the child process
  +      can't reaquire the lock.
  +
       * Must namespace protect all include/apr_foo.h headers.  Jon Travis
         has especially observed these including apr within Apache-1.3.
           Message-ID: <20020128100116.A4288@covalent.net>
  
  
  

Mime
View raw message