From owner-freebsd-hackers Fri Jul 31 10:44:46 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id KAA26151 for freebsd-hackers-outgoing; Fri, 31 Jul 1998 10:44:46 -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 KAA26145 for ; Fri, 31 Jul 1998 10:44:42 -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 NAA13956 for ; Fri, 31 Jul 1998 13:44:35 -0400 (EDT) (envelope-from mcgovern@spoon.beta.com) Message-Id: <199807311744.NAA13956@spoon.beta.com> To: hackers@FreeBSD.ORG Subject: O_SHLOCK and O_EXLOCK during open... (locking for devices?) Date: Fri, 31 Jul 1998 13:44:35 -0400 From: "Brian J. McGovern" Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Yup, me again with another dumb programming question.... I seem to be running in to problems when opeing up a device special file with either O_SHLOCK or O_EXLOCK. I get an error back (45) that the operation is not supported. My question, then, is, how can I lock, lets say a serial port, without having to go the route of lock-file creation, as many applications ignore these files anyhow? -Brian To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message