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:reply-to:from:to:references:in-reply-to
	:subject:date:message-id:mime-version:content-type
	:content-transfer-encoding; q=dns; s=default; b=rOiOIJvhlE3/1Fbn
	gL0Rwxk+SgxKY/n6fH6Ff6QxTNb4Uv9FE+s/PgrvlmTe7UMFngX7hxqBOgc8qry1
	kx2t9FRfZo6A1wtxRl7UIl4+ocCU0RpcriDa3IxPi1Dmjvk4F9rYa7LKs/KjIDpF
	PxhNpbAOuU4WKjZe1P8h/TZdRLg=
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:reply-to:from:to:references:in-reply-to
	:subject:date:message-id:mime-version:content-type
	:content-transfer-encoding; s=default; bh=mFBzvCIJ0NeyG86aSoquF3
	OD3QE=; b=XRpOqoqMQO2rg0BeSYxeYnRGE4oZvjQOFsjwhoPot6HN6AvKtwmayG
	VtSZuLmMVs4WCsJK2lhDTvl1t21lMG7sCv61IXHdFmn3z9EhPwaN8Klw+j9mh1E9
	NdQH0Q7nyQCGD/S6nLF+qwC1v8QGc+lv+1Q/J2wZ3r5jyuCzgoeAE=
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.6 required=5.0 tests=AWL,BAYES_00,RCVD_IN_DNSWL_NONE autolearn=ham version=3.3.2
X-HELO:	p3plsmtpa06-04.prod.phx3.secureserver.net
Reply-To:	<sbardwell AT lbmsys DOT com>
From:	"Steven Bardwell" <SBardwell AT lbmsys DOT com>
To:	<cygwin AT cygwin DOT com>
References:	<040201cf25c4$54e9cd20$febd6760$@lbmsys.com> <20140209192859 DOT GG2821 AT calimero DOT vinschen DOT de> <041d01cf25d2$6a59e5b0$3f0db110$@lbmsys.com> <20140209203825 DOT GJ2821 AT calimero DOT vinschen DOT de>
In-Reply-To:	<20140209203825.GJ2821@calimero.vinschen.de>
Subject:	RE: spawnv() unlocks files in the calling program
Date:	Sun, 9 Feb 2014 16:09:03 -0500
Message-ID:	<045801cf25db$2dc95af0$895c10d0$@lbmsys.com>
MIME-Version:	1.0
X-IsSubscribed:	yes

> 
> Ok, I can reproduce it, but it's too late to debug this today.
> 
> I have to say, though, that fcntl advisory locking is POSIX
> functionality, while the spawn functions are not.  In fact these dreaded
> spawn entry points are rather old stuff, which hasn't been tested for a
> long time.  FWIW, advisory file locking has never been tested with them,
> and the fact that it doesn't work as expected doesn't exactly disturb me.
> 
> 
> Corinna
> 
> --
Knowing this, I will use the posix_spawn() function -- I wanted to reduce the
number of fork() calls  in my application (because of the many warnings about
the complexity of the Cygwin implementation of fork() and reported problems
with it), but if spawnv() won't do what I need, then under the bus it goes.

Steve



--
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 -