From owner-freebsd-hackers Tue Apr 20 10: 6: 5 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from mercury.inktomi.com (mercury.inktomi.com [209.1.32.126]) by hub.freebsd.org (Postfix) with ESMTP id D1EFB15237 for ; Tue, 20 Apr 1999 10:06:00 -0700 (PDT) (envelope-from jplevyak@inktomi.com) Received: from proxydev.inktomi.com (proxydev.inktomi.com [209.1.32.44]) by mercury.inktomi.com (8.9.1a/8.9.1) with ESMTP id KAA22677 for ; Tue, 20 Apr 1999 10:03:40 -0700 (PDT) Received: (from jplevyak@localhost) by proxydev.inktomi.com (8.8.5/8.7.3) id KAA10756 for hackers@FreeBSD.org; Tue, 20 Apr 1999 10:03:33 -0700 (PDT) Message-ID: <19990420100333.B10370@proxydev.inktomi.com> Date: Tue, 20 Apr 1999 10:03:33 -0700 From: John Plevyak To: hackers@FreeBSD.org Subject: flock + kernel threads bug Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.93.2i Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Currently, kernel threads + flock does not work. The lock is not necessarily released with the multi-threaded application shuts down. I have a patch which I have been running for a month now with no problems; who might I send it to to get it reviewed/committed? It would greatly simplify the installation of our multi-threaded apps on FreeBSD if a kernel patch was not required. Not to mention a general increase in confidence to have them work with FreeBSD "out-of-the-box". john -- John Bradley Plevyak, PhD, jplevyak@inktomi.com, PGP KeyID: 051130BD Inktomi Corporation, 1900 S. Norfolk Street, Suite 310, San Mateo, CA 94403 W:(650)653-2830 F:(650)653-2889 P:(888)491-1332/5103192436.4911332@pagenet.net To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message