From owner-freebsd-hackers  Fri Jul 31 12:16:49 1998
Return-Path: <owner-freebsd-hackers@FreeBSD.ORG>
Received: (from majordom@localhost)
          by hub.freebsd.org (8.8.8/8.8.8) id MAA08309
          for freebsd-hackers-outgoing; Fri, 31 Jul 1998 12:16:49 -0700 (PDT)
          (envelope-from owner-freebsd-hackers@FreeBSD.ORG)
Received: from spoon.beta.com (mcgovern.ne.mediaone.net [24.128.106.170])
          by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id MAA08301
          for <hackers@freebsd.org>; Fri, 31 Jul 1998 12:16:46 -0700 (PDT)
          (envelope-from mcgovern@spoon.beta.com)
Received: from spoon.beta.com (mcgovern@localhost [127.0.0.1])
	by spoon.beta.com (8.8.8/8.8.8) with ESMTP id PAA14142;
	Fri, 31 Jul 1998 15:16:37 -0400 (EDT)
	(envelope-from mcgovern@spoon.beta.com)
Message-Id: <199807311916.PAA14142@spoon.beta.com>
To: Open Systems Networking <opsys@mail.webspan.net>
cc: hackers@FreeBSD.ORG
Subject: Re: O_SHLOCK and O_EXLOCK during open... (locking for devices?) 
In-reply-to: Your message of "Fri, 31 Jul 1998 14:55:19 EDT."
             <Pine.BSF.3.95.980731145432.7771A-100000@orion.webspan.net> 
Date: Fri, 31 Jul 1998 15:16:36 -0400
From: "Brian J. McGovern" <mcgovern@spoon.beta.com>
Sender: owner-freebsd-hackers@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG

Thanks for the feedback... uu_lock and family is possible to use, but it
will fail with applications that don't check or use the facility ( a lot
of poorly written ones). I need something thats more kernel-oriented, that
will catch a lock issue during the open() call. I'd even make the changes
in the driver(s), if required, but it appears the error is caused outside
of the driver open() call, and therefore I really can't hook in to it
until its too late.
	-Brian

To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-hackers" in the body of the message