Article View: comp.mail.misc
Article #3040Re: Symlink locking considered useless over NFS
From: Chip Salzenberg
Date: Mon, 22 Apr 1991 01:54
Date: Mon, 22 Apr 1991 01:54
16 lines
1269 bytes
1269 bytes
According to thurlow@convex.com (Robert Thurlow):
>C'mon Chip, flame in the right direction. The lack of support for
>O_EXCL in the create operation of NFS isn't a feature of statelessness,
>it's just a simple-minded protocol bug.
I don't understand. How can the server know that it's me
re-requesting an already-successful creation, and not some other
process on the client machine asking to create the same file?
(Please note that solutions based on keeping transaction info for the
last N seconds are NOT acceptable, as the network cable might be
disconnected for N+1 seconds.)
--
Brand X Industries Custodial, Refurbishing and Containment Service:
When You Never, Ever Want To See It Again [tm]
Chip Salzenberg <chip@tct.com>, <uunet!pdn!tct!chip>
Technical Details
Message-ID:
<28124239.17CE@tct.com>Path:
arc1-ca.pugleaf.net!utzoo!utgpu!news-server.csri.toronto.edu!cs.utexas.edu!uunet!pdn!tscs!tct!chipReferences:
<3064@cirrusl.UUCP> <280EE8A1.30D@tct.com> <thurlow.672093078@convex.convex.com>Show Full Headers
Complete Article Headers
Path: arc1-ca.pugleaf.net!utzoo!utgpu!news-server.csri.toronto.edu!cs.utexas.edu!uunet!pdn!tscs!tct!chip From: chip@tct.com (Chip Salzenberg) Newsgroups: comp.mail.misc,comp.protocols.nfs Subject: Re: Symlink locking considered useless over NFS Message-ID: <28124239.17CE@tct.com> Date: 22 Apr 91 01:54:01 GMT References: <3064@cirrusl.UUCP> <280EE8A1.30D@tct.com> <thurlow.672093078@convex.convex.com> Followup-To: comp.protocols.nfs Organization: Teltronics/TCT, Sarasota, FL Lines: 16