Mailing-List: contact cygwin-developers-help AT sourceware DOT cygnus DOT com; run by ezmlm List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-developers-owner AT sources DOT redhat DOT com Delivered-To: mailing list cygwin-developers AT sources DOT redhat DOT com To: cygwin-developers AT cygwin DOT com Subject: Re: fcntl(f, F_SETLK, &fl) problem on Cygwin 1.1.8(0.34/3/2) References: <200103030113 DOT CAA24952 AT fokus DOT gmd DOT de> Mime-Version: 1.0 (generated by tm-edit 7.106) Content-Type: text/plain; charset=US-ASCII From: Kazuhiro Fujieda Date: 05 Mar 2001 12:19:36 +0900 In-Reply-To: Joerg Schilling's message of Sat, 3 Mar 2001 02:13:42 +0100 (MET) Message-ID: Lines: 24 X-Mailer: Gnus v5.3/Emacs 19.34 >>> On Sat, 3 Mar 2001 02:13:42 +0100 (MET) >>> Joerg Schilling said: > VED (and similar nvi) does record locking of edited files by first > opening the file with O_RDWR and applying a record lock. Then it opens > the the file for reading and reads the file into the buffer. > > This definitely does not work with Cygwin on Win ME. > > - Will this work on Win NT ? No. The locking semantics in Cygwin is completely different from UNIX. A lock is acquired by a file descriptor, not by a process. This is the semantics of LockFile or LockFileEx invoked by the Cygwin DLL. > But then there should definitely a fix in cygwin or a hint in the FAQ. I think such a troublesome locking mechanism should be eliminated from the Cygwin DLL or should be noted by a document. ____ | AIST Kazuhiro Fujieda | HOKURIKU School of Information Science o_/ 1990 Japan Advanced Institute of Science and Technology