X-Recipient:	archive-cygwin AT delorie DOT com
DomainKey-Signature:	a=rsa-sha1; c=nofws; d=sourceware.org; h=list-id
	:list-unsubscribe:list-subscribe:list-archive:list-post
	:list-help:sender:date:from:to:message-id:in-reply-to:references
	:subject:mime-version:content-type:content-transfer-encoding; q=
	dns; s=default; b=GOYvLIYIzL1rfswPlYtQT1BKuPJEPK5dJYwjz+zw15GdPW
	LMOAKp5T5VPugwBcKx0m3hh4NWAan69q/LNKtmCd3XKq93UpcFesgKn+/5w3ZAoo
	cWcix05saGEKvXJJQ3cHgTWhDdcO+2aiXYde/XaoooL4o2NbfnEFDu394u8P0=
DKIM-Signature:	v=1; a=rsa-sha1; c=relaxed; d=sourceware.org; h=list-id
	:list-unsubscribe:list-subscribe:list-archive:list-post
	:list-help:sender:date:from:to:message-id:in-reply-to:references
	:subject:mime-version:content-type:content-transfer-encoding; s=
	default; bh=1/p0vIyNGrfhzxHuSY/Iq2MwnZI=; b=mggO/qiArmy1x/rKKewF
	MDk0lrj/CBQJPhPANq0x8mcp5AnilXppljGlKRFDNNQTr/zh8iHLzoFXgNW29cyd
	U6prErQ6sNQvmJKKf2Tfv/0bdX09guxqSopRSurEHOfhGU7zw5pF4V+WIw0Giwl+
	Hv81y/NZt7L2A6vmSC3wQEM=
Mailing-List:	contact cygwin-help AT cygwin DOT com; run by ezmlm
List-Id:	<cygwin.cygwin.com>
List-Subscribe:	<mailto:cygwin-subscribe AT cygwin DOT com>
List-Archive:	<http://sourceware.org/ml/cygwin/>
List-Post:	<mailto:cygwin AT cygwin DOT com>
List-Help:	<mailto:cygwin-help AT cygwin DOT com>, <http://sourceware.org/ml/#faqs>
Sender:	cygwin-owner AT cygwin DOT com
Mail-Followup-To:	cygwin AT cygwin DOT com
Delivered-To:	mailing list cygwin AT cygwin DOT com
Authentication-Results:	sourceware.org; auth=none
X-Virus-Found:	No
X-Spam-SWARE-Status:	No, score=0.8 required=5.0 tests=BAYES_00,FORGED_HOTMAIL_RCVD2,FREEMAIL_FROM,RCVD_IN_DNSWL_NONE,SPF_HELO_PASS,SPF_SOFTFAIL,URI_HEX autolearn=no version=3.3.2 spammy=elected, ended, sk:cygwin., assist
X-HELO:	n5.nabble.com
Date:	Sun, 27 May 2018 03:38:00 -0700 (MST)
From:	sin_vraal <sin_vraal AT hotmail DOT com>
To:	cygwin AT cygwin DOT com
Message-ID:	<1527417480694-0.post@n5.nabble.com>
In-Reply-To:	<CA+OMFi-XVLq7TUuB-V+zS71tCD70fCg_+hv6M6_5v=NHzO5trA@mail.gmail.com>
References:	<CA+OMFi_g3Vrj3JFzBxcu_dLLt9E1Tyzh2Yop1tqBaOy5_S-ztA AT mail DOT gmail DOT com> <CA+OMFi-XVLq7TUuB-V+zS71tCD70fCg_+hv6M6_5v=NHzO5trA AT mail DOT gmail DOT com>
Subject:	Re: httpd/sshd will not start due to "failed to create proxy mutex" error
MIME-Version:	1.0

I ended up having a similar problem with mod_rewrite. tapping in, in the
event someone else needs the assist.

>in httpd.conf: LoadModule rewrite_module modules/mod_rewrite.so
>error_log:  Function not implemented: AH00023: Couldn't create the
rewrite-map mutex


I solved with "Mutex flock:/etc/httpd/conf/mutex rewrite-map"

I've elected to use the 'flock' instead of 'file' or 'fcntl' simply b/c I
dont know what 'best' is for 'file' and fcntl in theory has a listed
problem, although unlikely.

I tested posixsem as well, and it works. although it says

apache documentation on mutex wrote
> Warning
> The semaphore ownership is not recovered if a thread in the process
> holding the mutex segfaults, resulting in a hang of the web server.

That does not sound appealing to me, thus flock.



--
Sent from: http://cygwin.1069669.n5.nabble.com/Cygwin-list-f3.html

--
Problem reports:       http://cygwin.com/problems.html
FAQ:                   http://cygwin.com/faq/
Documentation:         http://cygwin.com/docs.html
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple

- Raw text -