From owner-freebsd-hackers@FreeBSD.ORG Thu Jun 24 23:49:21 2004 Return-Path: Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 83B5616A4CE for ; Thu, 24 Jun 2004 23:49:21 +0000 (GMT) Received: from blitzen.qlo.com (blitzen.qlo.com [142.165.150.52]) by mx1.FreeBSD.org (Postfix) with ESMTP id 3D6B543D2D for ; Thu, 24 Jun 2004 23:49:21 +0000 (GMT) (envelope-from shurd@sasktel.net) Received: from stephens (hssx-yktn-59-202.sasknet.sk.ca [142.165.59.202]) by mail.qlo.com (SaskTel eMessaging Service) with ESMTPA id <0HZU001H47I7PN@mail.qlo.com> for freebsd-hackers@freebsd.org; Thu, 24 Jun 2004 17:49:20 -0600 (CST) Date: Thu, 24 Jun 2004 17:49:19 -0600 From: Stephen Hurd To: freebsd-hackers@freebsd.org Message-id: <20040624174919.46160f9e.shurd@sasktel.net> MIME-version: 1.0 X-Mailer: Sylpheed version 0.9.12 (GTK+ 1.2.10; i386-portbld-freebsd4.9) Content-type: text/plain; charset=US-ASCII Content-transfer-encoding: 7BIT Subject: Locking: kern/50827 X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 24 Jun 2004 23:49:21 -0000 Well, possibly due to editorial content, kern/50827 has been completely ignored. Not sure exactly the correct method of bringing something like this up, but am I the only one who finds flock(), dotlock, and fcntl() locks insufficient for their needs? Originally, this patch resulted from porting a multi-threaded Win32 program to *nix... however, I've since used the features it in a number of programs (for FreeBSD only of course) with good success. It really makes locking behave as expected. Has anyone looked at this? Does anyone have any comments? http://www.freebsd.org/cgi/query-pr.cgi?pr=kern/50827