Path: utzoo!utgpu!jarvis.csri.toronto.edu!cs.utexas.edu!swrinde!zaphod.mps.ohio-state.edu!pacific.mps.ohio-state.edu!tut.cis.ohio-state.edu!ucbvax!decwrl!ogicse!emory!hubcap!ncrcae!sauron!wescott
From: wescott@Columbia.NCR.COM (Mike Wescott)
Newsgroups: comp.sys.ncr
Subject: Re: Why do the 2.01.01 sa scripts disallow moving /tmp?
Message-ID: <2039@sauron.Columbia.NCR.COM>
Date: 7 Mar 90 20:12:14 GMT
References: <1990Mar1.185600.8816@is.uu.no>
Sender: news@sauron.Columbia.NCR.COM
Reply-To: wescott@micky.Columbia.NCR.COM (Mike Wescott)
Organization: E&M-Columbia, NCR Corp, W Columbia, SC
Lines: 20

In article <1990Mar1.185600.8816@is.uu.no> ra@is.uu.no (Robert Andersson) writes:
> I see no reason why the sa scripts should disallow moving /tmp to an
> unused partition.  [ ... ]   In my opinion it often makes sense to
> dedicate a partition to /tmp

I don't know exactly why it's excluded, but yes the system runs with
/tmp on another partition.  Often performance is increased and root
filesystem problems decreased.

One reasonable explanation is that /tmp is often used in "single user",
i.e. run state 0, and files left in /tmp disappear while a filesystem
is mounted there.  These files can slowly eat up disk space if they are
not periodically cleared out.

Another possibility is the practice that some adminstrative scripts have
of leaving information in files in /tmp as signals across run-state 
transitions.
--
	-Mike Wescott
	 mike.wescott@ncrcae.Columbia.NCR.COM