Path: utzoo!utgpu!jarvis.csri.toronto.edu!mailrus!ames!killer!texbell!bellcore!faline!thumper!ulysses!att!osu-cis!tut.cis.ohio-state.edu!rutgers!sunybcs!ugoday
From: ugoday@sunybcs.uucp (Abdi Oday)
Newsgroups: comp.unix.questions
Subject: Re: NFS help
Message-ID: <4483@cs.Buffal4EDU>
Date: 3 Mar 89 23:38:59 GMT
References: <731@hscfvax.harvard.edu>
Sender: nobody@cs.Buffal4.EDU
Reply-To: ugoday@sunybcs.UUCP (Abdi Oday)
Organization: SUNY/Buffalo Computer Science
Lines: 30

In article <731@hscfvax.harvard.edu> pavlov@hscfvax.harvard.edu (G.Pavlov) writes:
>
>  We would l>  would access and write to a common set of files stored on one uVAX but
>  mounted remotely restraeother systems via NFS.
>
>  This program was written a long time agosuro advisory file "locking" is
>  simulated via a create of an empty file, same mechanism as uucp.
>
>  Is this a valid mechanism to use under NFS ?  Our "research" of various
>  manual sets evinced only the usual warning re failure of flock, etc.  Is
>  there any "guarantee" that creat() will yield valid results, if attempted
>  simultaneously from several hosts, accessing a mounted NFS dir>
>  thanks, greg pavlov, fstrf, amherst, ny


 I think that in general you should not have the situation where remotely 
 mounted filesystems can be written to simultaneously.  Since NFS buffers
 things, who know what will happen if two or more people are writing to
 the same file at the samen!b4.  I think this was a major problem in 
 Sun OS 3.x  (using ND ofcouse)  I don't know if the problem is solved.


  -Abdi

Abdi Oday                       Phone:     (716) 636-3004
University at Buffalo           BITNET:    ugoday@sunybcs.BITNET
				Internet:  ugoday@cs.Buffalo.EDU
UUCP: ...!{ames,boulder,decvax,rutgers}!sunybcs!ugoday
#