:Somehow you need to get a lock.
:
:> You mean have one program make a fcntl call that causes other
:> programs to return an error or block if they try to open that
:> file while the first program holds an open descriptor?
:
:Correct. I suppose it's worth discussing what the default should be.
:Should they get EAGAIN or block? Obviously you'd want a way of
:specifying which, but there would have to be a default for
:non-lock-aware programs. I think I'd go for blocking; it's less error
:prone.
:
:Greg
I dunno, it sounds pretty icky to me. I would redesign whatever you
are doing that requires mandatory locks to use advisory locks instead.
It can be as simple as a wrapper around whatever program your users are
running that is causing whatever the problem is.
-Matt
Matthew Dillon
<[EMAIL PROTECTED]>
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-hackers" in the body of the message
