This is the mail archive of the
mailing list for the Cygwin project.
Re: sqlite3: bug with monotone
- From: Corinna Vinschen <corinna-cygwin at cygwin dot com>
- To: cygwin at cygwin dot com
- Date: Fri, 31 May 2013 11:22:28 +0200
- Subject: Re: sqlite3: bug with monotone
- References: <51A6B6EB dot 6050309 at users dot sourceforge dot net> <loom dot 20130530T122354-144 at post dot gmane dot org> <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>
- Reply-to: cygwin at cygwin dot com
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
- 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
- For anything else, http://cygwin.com/acronyms/#PTC
Does that sound ok?
Corinna Vinschen Please, send mails regarding Cygwin to
Cygwin Maintainer cygwin AT cygwin DOT com
Problem reports: http://cygwin.com/problems.html
Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple