Mailing-List:	contact cygwin-help AT cygwin DOT com; run by ezmlm
List-Subscribe:	<mailto:cygwin-subscribe AT cygwin DOT com>
List-Archive:	<http://sourceware.org/ml/cygwin/>
List-Post:	<mailto:cygwin AT cygwin DOT com>
List-Help:	<mailto:cygwin-help AT cygwin DOT com>, <http://sourceware.org/ml/#faqs>
Sender:	cygwin-owner AT cygwin DOT com
Mail-Followup-To:	cygwin AT cygwin DOT com
Delivered-To:	mailing list cygwin AT cygwin DOT com
Message-ID:	<412DDF4D.2030603@x-ray.at>
Date:	Thu, 26 Aug 2004 15:02:05 +0200
From:	Reini Urban <rurban AT x-ray DOT at>
User-Agent:	Mozilla/5.0 (Windows; U; Windows NT 5.0; de-AT; rv:1.8a2) Gecko/20040714
MIME-Version:	1.0
To:	cygwin AT cygwin DOT com
Subject:	Re: F_ULOCK, F_LOCK, F_TLOCK, F_TEST missing in unistd.h
References:	<4215658170 DOT 20040826103850 AT familiehaase DOT de> <20040826090950 DOT GZ27978 AT cygbert DOT vinschen DOT de> <231908231281 DOT 20040826124602 AT familiehaase DOT de> <20040826113947 DOT GD27978 AT cygbert DOT vinschen DOT de>
In-Reply-To:	<20040826113947.GD27978@cygbert.vinschen.de>
X-IsSubscribed:	yes

Corinna Vinschen schrieb:
> I have already lockf kernel code from FreeBSD in my local sandbox since
> I began working on that earlier this year at one point.  The most missing
> resources are spare time and a good idea how to share the lock data
> between processes in a *sensible* way.  The simple appraoch would use
> Cygserver to keep track of lock data, but I really don't want to involve
> Cygserver in file I/O.

but lockf isn't used that often.
why not KISS style for the start?

-- 
Reini Urban
http://xarch.tu-graz.ac.at/home/rurban/

--
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple
Problem reports:       http://cygwin.com/problems.html
Documentation:         http://cygwin.com/docs.html
FAQ:                   http://cygwin.com/faq/

- Raw text -