Received: (qmail 16977 invoked by uid 501); 16 Oct 2000 10:03:35 -0000
Message-Id: <20001016100335.16976.qmail@locus.apache.org>
Date: 16 Oct 2000 10:03:35 -0000
From: Anthony Howe <achowe@snert.com>
Reply-To: achowe@snert.com
To: submit@bugz.apache.org
Subject: Missing functionality for all ap_*_mutex() on Linux.
X-Send-Pr-Version: 3.110

>Number:         6689
>Category:       apache-api
>Synopsis:       Missing functionality for all ap_*_mutex() on Linux.
>Confidential:   no
>Severity:       non-critical
>Priority:       medium
>Responsible:    apache
>State:          closed
>Quarter:        
>Keywords:       
>Date-Required:
>Class:          support
>Submitter-Id:   apache
>Arrival-Date:   Mon Oct 16 03:10:00 PDT 2000
>Closed-Date:    Thu Oct 19 01:49:08 PDT 2000
>Last-Modified:  Thu Oct 19 01:49:08 PDT 2000
>Originator:     achowe@snert.com
>Release:        1.3.12
>Organization:
>Environment:
Cobalt Qube 1 running Redhat Linux on MIPS.

Linux mail.snert.net 2.0.34C52_SK #1 Tue Nov 30 18:14:40 PST 1999 mips unknown
>Description:
The ap_*_mutex() family of functions are all #define to nothing for
process-based multitasking.  However, these functions appear to exist in
another form within http_main.c, accept_mutex_*() family.  Why #define, when
the code exists in some variant elsewhere within Apache?

Support for the ap_*_mutex() family would facilitate module writers who need to
use and control access to shared memory, such as mod_throttle, in a portable
fashion.

BTW an API for shared memory support would also be nice.
>How-To-Repeat:

>Fix:
Convert the accept_mutex_*() functions within http_main.c into ap_*_mutex().
>Release-Note:
>Audit-Trail:
State-Changed-From-To: open-closed
State-Changed-By: fanf
State-Changed-When: Thu Oct 19 01:49:08 PDT 2000
State-Changed-Why:
All of this code has been completely rewritten for 2.0 so
this report is no longer relevant. We aren't doing this
kind of maintenance on 1.3.
>Unformatted:
 [In order for any reply to be added to the PR database, you need]
 [to include <apbugs@Apache.Org> in the Cc line and make sure the]
 [subject line starts with the report component and number, with ]
 [or without any 'Re:' prefixes (such as "general/1098:" or      ]
 ["Re: general/1098:").  If the subject doesn't match this       ]
 [pattern, your message will be misfiled and ignored.  The       ]
 ["apbugs" address is not added to the Cc line of messages from  ]
 [the database automatically because of the potential for mail   ]
 [loops.  If you do not include this Cc, your reply may be ig-   ]
 [nored unless you are responding to an explicit request from a  ]
 [developer.  Reply only with text; DO NOT SEND ATTACHMENTS!     ]