Xref: utzoo comp.mail.misc:5281 comp.protocols.nfs:2197
Path: utzoo!utgpu!news-server.csri.toronto.edu!rpi!dali.cs.montana.edu!ogicse!intelhf!ichips!iwarp.intel.com!gargoyle!chinet!les
From: les@chinet.chi.il.us (Leslie Mikesell)
Newsgroups: comp.mail.misc,comp.protocols.nfs
Subject: Re: Symlink locking considered useless over NFS
Message-ID: <1991Apr23.040610.23159@chinet.chi.il.us>
Date: 23 Apr 91 04:06:10 GMT
References: <3064@cirrusl.UUCP> <280EE8A1.30D@tct.com> <3074@cirrusl.UUCP>
Organization: Chinet - Chicago Public Access UNIX
Lines: 17

In article <3074@cirrusl.UUCP> Rahul Dhesi <dhesi@cirrus.COM> writes:
>In <280EE8A1.30D@tct.com> chip@tct.com (Chip Salzenberg) writes:

>>This "solution" is nothing of the kind.
>>NFS can report failure on a symlink creation (or on directory
>>creation) even if the operation succeeds.

>How about calling it "the closest thing to a solution that has yet been
>seen on Usenet"?

There is some discussion in comp.unix.shell about using
 (umask 777; echo >file) || .... failure code...
as an attempt to get a more or less atomic operation in spite
of NFS, but I don't see how it can work if you run as root.

Les Mikesell
  les@chinet.chi.il.us