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=DmqEYTDaUqZjLoTiSXahx9fENh8OtXG9+VKAgB0giwLf2RDVVt+Sj wtDt5qEk5nXAmKueCJwkM1W04EPcNnxzAVFQa/JIKwOA1/4yk0ADUIsyCQ73MVdt 3Che7KGUrW4kyoewrh3jNqYwJJie/CCwIyUVL6Pc9KmloXOJA16D7k= 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=cO0jUfSvYol+YDpm2Zqolgzvrlo=; b=pLGxRMbs1Xt1BXi1d7mS7KfOgYu1 F0Lmqwv9FIj+bnDjmqpte3An2GUOoJgkPBKbdonlLNjFxRbIfqjQsTVA5x2eg+VM q8tA/gEqU5AyVQJWqs/w3146O2ou69xnZ7ydl77mlGAAPo1jOFP5SCpY+8TGCDf4 Gk/8kabi7bAz50o= Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm List-Id: List-Subscribe: List-Archive: List-Post: List-Help: , 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=-1.8 required=5.0 tests=AWL,BAYES_00,TW_FC autolearn=ham version=3.3.1 Date: Fri, 31 May 2013 11:22:28 +0200 From: Corinna Vinschen To: cygwin AT cygwin DOT com Subject: Re: sqlite3: bug with monotone Message-ID: <20130531092228.GB30659@calimero.vinschen.de> Reply-To: cygwin AT cygwin DOT com Mail-Followup-To: cygwin AT cygwin DOT com References: <51A6B6EB DOT 6050309 AT users DOT sourceforge DOT net> <51A7862F DOT 1070507 AT etr-usa DOT com> <51A7D47E DOT 3050502 AT users DOT sourceforge DOT net> <51A7F547 DOT 6020509 AT etr-usa DOT com> MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Disposition: inline In-Reply-To: <51A7F547.6020509@etr-usa.com> User-Agent: Mutt/1.5.21 (2010-09-15) On May 30 18:56, Warren Young wrote: > 1. We continue waiting for someone to to implement a per-process or > per-subtree mandatory locking feature in Cygwin, so that "Unix mode" > SQLite on Cygwin can be configured to cooperate with native SQLite. What kind of locking does sqlite use on Cygwin: [ ] POSIX fcntl locks [ ] BSD flock locks [ ] Old POSIX lockf locks? Here's a proposal: - Only add optional mandatory locking to fcntl and flock locks, not for lockf locks. - Add a flag F_MDLCK which can be or'ed to struct flock's l_type. - Add a flag LOCK_MD which can be or'ed to the 2nd parameter to flock(2). - Using these flags, I'll resurrect the old pre-Cygwin 1.7 locking code which does NOT support F_GETLK. I will try, but I can also not guarantee that a blocking, mandatory lock call will be interruptible by signals. - For anything else, http://cygwin.com/acronyms/#PTC Does that sound ok? 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