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

jerenkrantz    01/12/12 02:05:54

  Modified:    .        STATUS
  Log:
  Not a big deal, but worth noting.  If anyone has an idea on how to
  detect this, it'd be general goodness to error out when we create
  the lock rather than waiting to error out when acquiring the lock.
  
  Revision  Changes    Path
  1.79      +6 -1      apr/STATUS
  
  Index: STATUS
  ===================================================================
  RCS file: /home/cvs/apr/STATUS,v
  retrieving revision 1.78
  retrieving revision 1.79
  diff -u -r1.78 -r1.79
  --- STATUS	2001/12/12 08:33:39	1.78
  +++ STATUS	2001/12/12 10:05:54	1.79
  @@ -1,5 +1,5 @@
   APACHE PORTABLE RUNTIME (APR) LIBRARY STATUS:			-*-text-*-
  -Last modified at [$Date: 2001/12/12 08:33:39 $]
  +Last modified at [$Date: 2001/12/12 10:05:54 $]
   
   Release:
   
  @@ -274,6 +274,11 @@
         begin to migrate the old API to be implemented on top of the
         new one, or just decide to get rid of it altogether.
         
  +    * FreeBSD returns 45 (EOPNOTSUPP) when the lockfile is on a NFS
  +      partition when you call fcntl(F_SETLKW).  It may be good if we 
  +      can somehow detect this and error out when creating the lock
  +      rather than waiting for the error to occur when acquiring lock.
  +
   Documentation that needs writing:
   
       * API documentation