On Mon, Aug 23, 1999 at 11:16:21PM -0400, Chuck Robey wrote:
> On Mon, 23 Aug 1999, Christopher Masto wrote:
>
> > Bleah.. I can't count the number of times I've seen idiotic code like:
> >
> > open file
> > read data
> > close file
> > open file for write
> > write data
> > close file
> >
> > Mandatory locking of the type above doesn't force such a thing to work.
>
> What has that code you show above got to do with mandatory locking?
> You completely missed the explicit locking calls that you have to make,
> to get and release the locks. If you don't make the call, and you have
> madatory locking, then your process will sleep until someone else
> releases the lock;
Exactly. You said that mandatory locking means that user A's correct
use of locking means that user B doesn't have to be careful. That's
not the case, since A can step in between B's read and write. A's
mandatory lock doesn't help.
I don't see the use for it.
--
Christopher Masto Senior Network Monkey NetMonger Communications
[EMAIL PROTECTED] [EMAIL PROTECTED] http://www.netmonger.net
Free yourself, free your machine, free the daemon -- http://www.freebsd.org/
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-hackers" in the body of the message
