Path: utzoo!utgpu!utstat!jarvis.csri.toronto.edu!mailrus!cornell!uw-beaver!rice!sun-spots-request
From: bet@orion.mc.duke.edu (Bennett Todd)
Newsgroups: comp.sys.sun
Subject: Re: Sharing /tmp through NFS
Message-ID: <8901231518.AA25744@orion.mc.duke.edu>
Date: 31 Jan 89 14:22:56 GMT
Sender: usenet@rice.edu
Organization: Sun-Spots
Lines: 21
Approved: Sun-Spots@rice.edu
Original-Date: Mon, 23 Jan 89 10:18:42 EST
X-Sun-Spots-Digest: Volume 7, Issue 129, message 1 of 10

As Gregory Bond points out, there are problems with sharing an NFS-mounted
/tmp directory over a network. The performance question is a real issue,
except that diskless machines are getting to everything via the network
anyway. I hate having /tmp be on root, and don't want a slew of additional
partitions to give every machine its own /tmp, so I had every machine
mount up one common /tmp partition via NFS. PID collisions could
potentially have been a (rare) occurance; what bit me immediately was
cutting and pasting between windows. Apparantly that is routed through a
file (/tmp/winselection?) that has a fixed name.  It was really amusing
when users were cutting and pasting from each other's windows:-).

My solution was to have everyone mount a common tmp filesystem on
/nfs/tmp. This filesystem had subdirectories for each machine, so machine
"orion" had a directory /nfs/tmp/orion. Finally I put symlinks in the root
directories for each machine pointing to their tmp subdirectory. I haven't
had any problems since. I really like sharing /tmp; whereas for one
machine I'd want to have at least 4-5M free for tmp files, I haven't run
into any problems sharing ~20M among a dozen machines. 

-Bennett
bet@orion.mc.duke.edu