Google Groups no longer supports new Usenet posts or subscriptions. Historical content remains viewable.
Dismiss

NFSv3 O_EXCL

5 views
Skip to first unread message

ri...@snowhite.cis.uoguelph.ca

unread,
Jul 25, 2000, 3:00:00 AM7/25/00
to
The problem with the change you suggest is that a lot of programs don't
expect open()s with O_EXCL to always fail (which is what will happen
after the change you suggest for servers that don't support the option).

rick

Thor Lancelot Simon

unread,
Jul 25, 2000, 3:00:00 AM7/25/00
to

It seems to me that it's a lot better than the alternative, having the open
"succeed" but not be exclusive! After all, you don't ask for O_EXCL if you
don't care whether the operation's exclusive or not.

--
Thor Lancelot Simon t...@rek.tjls.com
"And where do all these highways go, now that we are free?"

Manuel Bouyer

unread,
Jul 26, 2000, 3:00:00 AM7/26/00
to
On Tue, Jul 25, 2000 at 05:57:12PM -0400, ri...@snowhite.cis.uoguelph.ca wrote:
> The problem with the change you suggest is that a lot of programs don't
> expect open()s with O_EXCL to always fail (which is what will happen
> after the change you suggest for servers that don't support the option).

program opening a file with O_EXCL expect a specific, well defined service
from the filesystem. If the filesystem (or in this case the NFS server) can't
offer this service; then this program can't work reliably. I don't think it's
good to allow it to run anyway. The only problem I can see here is that
EOPNOTSUPP doesn't point to the server, unless you really know what's up.

Now, a program opening a file O_EXCL when it doesn't need it is brocken.

--
Manuel Bouyer, LIP6, Universite Paris VI. Manuel...@lip6.fr
--

0 new messages