Path: utzoo!attcan!uunet!lll-winken!ncis.llnl.gov!ncis!helios.ee.lbl.gov!pasteur!agate!bionet!csd4.milw.wisc.edu!mailrus!cornell!uw-beaver!rice!sun-spots-request
From: munnari!melba.oz.au!gnb@uunet.uu.net (Gregory N. Bond)
Newsgroups: comp.sys.sun
Subject: Re: Sharing /tmp through NFS
Message-ID: <71@melba.oz>
Date: 18 Jan 89 01:04:50 GMT
References: <8901051732.AA24869@fs3.cs.rpi.edu>
Sender: usenet@rice.edu
Organization: Sun-Spots
Lines: 24
Approved: Sun-Spots@rice.edu
Original-Date: 12 Jan 89 22:08:51 GMT
X-Sun-Spots-Digest: Volume 7, Issue 108, message 3 of 16

In article v7n97/11 weltyc@fs3.cs.rpi.edu (Christopher A. Welty) writes:
>I wonder if anyone has tried using one NFS-mounted /tmp directory for a
>group of machines.  I forsee possible problems with temp files names that
>have the same name, it would seem like a trivial thing to check for - but
>does sunos do it....

I would NOT recommend this for two reasons:

1) It would be SLOW.  /tmp is one of those places you use a LOT, and
making it NFS mounted would have quite a noticable impact in editors among
other things.

2) It would cause problems with duplicate names.  Many shell scripts (and
I assume programs) make unique tmp filenames based on the PID which is
unique on a single workstation, but NOT guaranteed unique across a
network.  Imagine if two users started vi on different files on different
machines, but with the same PID - disaster, or at least confusion, as both
editors proceed to use the same tmp file to edit from....

Greg.

Gregory Bond, Burdett Buckeridge & Young Ltd, Melbourne, Australia
Internet: gnb@melba.bby.oz.au    non-MX: gnb%melba.bby.oz@uunet.uu.net
Uucp: {uunet,mnetor,pyramid,ubc-vision,ukc,mcvax,...}!munnari!melba.bby.oz!gnb