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 Message-ID: <412DDF4D.2030603@x-ray.at> Date: Thu, 26 Aug 2004 15:02:05 +0200 From: Reini Urban User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.0; de-AT; rv:1.8a2) Gecko/20040714 MIME-Version: 1.0 To: cygwin@cygwin.com Subject: Re: F_ULOCK, F_LOCK, F_TLOCK, F_TEST missing in unistd.h References: <4215658170.20040826103850@familiehaase.de> <20040826090950.GZ27978@cygbert.vinschen.de> <231908231281.20040826124602@familiehaase.de> <20040826113947.GD27978@cygbert.vinschen.de> In-Reply-To: <20040826113947.GD27978@cygbert.vinschen.de> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit 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/