Mailing-List:	contact cygwin-help AT sourceware DOT cygnus DOT com; run by ezmlm
List-Subscribe:	<mailto:cygwin-subscribe AT sources DOT redhat DOT com>
List-Archive:	<http://sources.redhat.com/ml/cygwin/>
List-Post:	<mailto:cygwin AT sources DOT redhat DOT com>
List-Help:	<mailto:cygwin-help AT sources DOT redhat DOT com>, <http://sources.redhat.com/ml/#faqs>
Sender:	cygwin-owner AT sources DOT redhat DOT com
Delivered-To:	mailing list cygwin AT sources DOT redhat DOT com
Date:	Mon, 9 Jul 2001 10:28:28 +0200
From:	Corinna Vinschen <cygwin AT cygwin DOT com>
To:	cygwin AT cygwin DOT com
Subject:	Re: file locking (F_GETLK) porting workaround anyone???
Message-ID:	<20010709102828.H8578@cygbert.vinschen.de>
Mail-Followup-To:	cygwin AT cygwin DOT com
References:	<3B4961EE AT epostleser DOT online DOT no>
Mime-Version:	1.0
User-Agent:	Mutt/1.2.5i
In-Reply-To:	<3B4961EE@epostleser.online.no>; from hardon@online.no on Mon, Jul 09, 2001 at 09:56:20AM +0200

On Mon, Jul 09, 2001 at 09:56:20AM +0200, hardon wrote:
> Any known workaround for the unimplemented F_GETLK, file locking func???
> Whats the big deal with this thing anyway??
> If we don't need the lockers pid, just try std. lock and check for errors, 
> right??

You're welcome to contribute F_GETLK and F_SETLK(W) in Cygwin if you've
found a way to implement them correctly.

Corinna

-- 
Corinna Vinschen                  Please, send mails regarding Cygwin to
Cygwin Developer                                mailto:cygwin AT cygwin DOT com
Red Hat, Inc.

--
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/

- Raw text -