Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm 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-Lotus-FromDomain: COMPUTRITION From: Fred_Smith AT computrition DOT com To: cygwin AT cygwin DOT com Message-ID: <85256CA3.0051407B.00@cinote.computrition.com> Date: Fri, 3 Jan 2003 10:02:07 -0500 Subject: Re: cygwin Digest 2 Jan 2003 23:32:57 -0000 Issue 2457 Mime-Version: 1.0 Content-type: text/plain; charset=us-ascii > > Message-ID: <20030102165207 DOT 34622 DOT qmail AT web14708 DOT mail DOT yahoo DOT com> > Date: Thu, 2 Jan 2003 08:52:07 -0800 (PST) > From: Robert Bercik > Subject: lockf() or flock() support? > To: cygwin AT cygwin DOT com > MIME-Version: 1.0 > Content-Type: text/plain; charset=us-ascii > > > I'm porting an application that uses lockf() to cygwin > and it doesn't appear that either are supported on > cygwin. If so i can't seem to find which library they > are contained in. Anybody have any luck with either of > these? > > thanks, > -Rob You could implement your own lockf() as a wrapper around fcntl(), assuming that enough of fcntl() functionality actually exists (I did it once upon a time for a really old LInux that didn't have lockf, and it actually worked! however I don't own the code so I can't send it to you--it wasn't hard, less than 100 lines of code, including whitespace and comments.) I have no personal knowledge of the completeness of cygwin's fcntl() so YMMV. Good luck! Fred -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Bug reporting: http://cygwin.com/bugs.html Documentation: http://cygwin.com/docs.html FAQ: http://cygwin.com/faq/