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 Date: Sun, 4 Mar 2001 23:55:58 -0500 From: Christopher Faylor To: cygwin-developers AT cygwin DOT com Subject: Re: fcntl(f, F_SETLK, &fl) problem on Cygwin 1.1.8(0.34/3/2) Message-ID: <20010304235558.C8103@redhat.com> Reply-To: cygwin-developers AT cygwin DOT com Mail-Followup-To: cygwin-developers AT cygwin DOT com References: <200103030113 DOT CAA24952 AT fokus DOT gmd DOT de> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.3.11i In-Reply-To: ; from fujieda@jaist.ac.jp on Mon, Mar 05, 2001 at 12:19:36PM +0900 On Mon, Mar 05, 2001 at 12:19:36PM +0900, Kazuhiro Fujieda wrote: >>>> 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. I appreciate the clarification but, as I've noted, if a change in documentation or source code is appropriate, then I expect someone in this mailing list to provide it. Maybe you and Joerg can work together to provide something appropriate? cgf