Mailing-List: contact cygwin-help@cygwin.com; run by ezmlm List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-owner@cygwin.com Mail-Followup-To: cygwin@cygwin.com Delivered-To: mailing list cygwin@cygwin.com Date: Thu, 26 Aug 2004 13:39:47 +0200 From: Corinna Vinschen To: cygwin@cygwin.com Subject: Re: F_ULOCK, F_LOCK, F_TLOCK, F_TEST missing in unistd.h Message-ID: <20040826113947.GD27978@cygbert.vinschen.de> Reply-To: cygwin@cygwin.com Mail-Followup-To: cygwin@cygwin.com References: <4215658170.20040826103850@familiehaase.de> <20040826090950.GZ27978@cygbert.vinschen.de> <231908231281.20040826124602@familiehaase.de> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <231908231281.20040826124602@familiehaase.de> User-Agent: Mutt/1.4.2i On Aug 26 12:46, Gerrit P. Haase wrote: > Corinna wrote: > > Hey, are you going to implement lockf for Cygwin? :-) > > Ummm, I wasn't aware that I want to implement it;) > I'll do some research, maybe we can take it easily from FreeBSD? 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. Corinna -- Corinna Vinschen Please, send mails regarding Cygwin to Cygwin Project Co-Leader mailto:cygwin@cygwin.com Red Hat, Inc. -- 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/