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:subject:message-id:reply-to
	:references:mime-version:content-type:in-reply-to; q=dns; s=
	default; b=CxTT+ivmOQxSar/cGk0smLZyCmrvPj192WYkyEyNl86mCakFfpIW2
	oI9ZaUrE8qq7ditzXZCOV+ZQ/+CjAqmLPU9uuyDT9St6tKlVLrlnTSQpLMh+oGDX
	Yy3CbhWlp5Y8Zk7OCxndVl+RrWt9FlME1Hfs5tIzKlch5Ibi4KVSmg=
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:subject:message-id:reply-to
	:references:mime-version:content-type:in-reply-to; s=default;
	 bh=Z+XESLb4OlgAUFuD7xOe6H4wCu0=; b=LU+tyl+5JTonmKObaQdYgePJ2AXZ
	Ug6f0lnTWCn0KsFRBgAouBvU2Mz597Xl1aK4GXQ1Z3c2Wb4yi6t2YMdTesq1JUrq
	tCMk1bRN73PQ6Es/X6DSFebGbfLIAkhb69Srn6O0S3MD1W4WmaeH4j5/GJ8sm6S3
	Cwqc9XptBOhaqi8=
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
X-Spam-SWARE-Status: No, score=0.1 required=5.0 tests=AWL,BAYES_50,RDNS_NONE autolearn=no version=3.3.1
Date: Fri, 19 Jul 2013 14:02:42 +0200
From: Corinna Vinschen <corinna-cygwin AT cygwin DOT com>
To: cygwin AT cygwin DOT com
Subject: Re: sqlite defect
Message-ID: <20130719120242.GH20871@calimero.vinschen.de>
Reply-To: cygwin AT cygwin DOT com
Mail-Followup-To: cygwin AT cygwin DOT com
References: <trinity-1068d666-3dec-43c9-8453-39c7cae3a94c-1374102947415 AT 3capp-gmx-bs33> <51E74AB4 DOT 7010508 AT etr-usa DOT com> <ks87ur$nle$1 AT ger DOT gmane DOT org> <20130718085953 DOT GC9628 AT calimero DOT vinschen DOT de> <ksa6bs$ac9$1 AT ger DOT gmane DOT org> <20130719100329 DOT GC20871 AT calimero DOT vinschen DOT de> <20130719100809 DOT GD20871 AT calimero DOT vinschen DOT de> <ksb4cn$cp8$1 AT ger DOT gmane DOT org> <20130719113009 DOT GE20871 AT calimero DOT vinschen DOT de> <ksb9be$2ss$1 AT ger DOT gmane DOT org>
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Disposition: inline
In-Reply-To: <ksb9be$2ss$1@ger.gmane.org>
User-Agent: Mutt/1.5.21 (2010-09-15)

On Jul 19 20:53, jojelino wrote:
> On 2013-07-19 PM 8:30, Corinna Vinschen wrote:
> >A valid testcase would help a lot, though.  What you meant to do
> >was calling flock with LOCK_EX|LOCK_NB.
> >
> that's what exactly sqlite3 that uses the mandatory-locking did.
> reproducing the behavior was i meant to do.
> >And then again, your testcase works as designed.  Not by me, but by
> >Microsoft.  You can't overwrite an existing lock, even if hold by the
> >same file handle.  See http://cygwin.com/cygwin-api/std-notes.html
> >
> Yes. the testcase works without mandatory locking. so i hope next
> sqlite3 release doesn't use mandatory locking feature of cygwin.
> someone who have plenty of time to waste digging into sqlite3 source
> code would come with workaround to the problem.

There *is* a workaround:

  export CYGWIN_SQLITE_LOCKING=posix

See http://cygwin.com/ml/cygwin-announce/2013-06/msg00014.html


Corinna

-- 
Corinna Vinschen                  Please, send mails regarding Cygwin to
Cygwin Maintainer                 cygwin AT cygwin DOT com
Red Hat

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