Date: Thu, 6 Aug 1998 00:49:08 -0500 (CDT) From: Joel Ray Holveck <joelh@gnu.org> To: mcgovern@spoon.beta.com Cc: hackers@FreeBSD.ORG Subject: Re: O_SHLOCK and O_EXLOCK during open... (locking for devices?) Message-ID: <199808060549.AAA13226@detlev.UUCP> In-Reply-To: <199807311744.NAA13956@spoon.beta.com> (mcgovern@spoon.beta.com) References: <199807311744.NAA13956@spoon.beta.com>
next in thread | previous in thread | raw e-mail | index | archive | help
> Yup, me again with another dumb programming question.... Yup, me again with another late answer.... > 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? O_SHLOCK and O_EXLOCK are advisory, not mandatory. In other words, the apps are going to ignore them anyway. Lock files are the way to go. Best, joelh -- Joel Ray Holveck - joelh@gnu.org - http://www.wp.com/piquan Fourth law of programming: Anything that can go wrong wi sendmail: segmentation violation - core dumped To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?199808060549.AAA13226>