Xref: utzoo comp.unix.questions:6194 comp.sys.att:2843
Path: utzoo!mnetor!uunet!husc6!bbn!rochester!PT.CS.CMU.EDU!IUS1.CS.CMU.EDU!edw
From: edw@IUS1.CS.CMU.EDU (Eddie Wyatt)
Newsgroups: comp.unix.questions,comp.sys.att
Subject: Re: NO SPACE  Error message
Message-ID: <1206@PT.CS.CMU.EDU>
Date: 23 Mar 88 18:24:13 GMT
References: <225@mccc.UUCP> <995@mcgill-vision.UUCP>
Sender: netnews@PT.CS.CMU.EDU
Organization: Carnegie-Mellon University, CS/RI
Lines: 19
Keywords: 3b2/400, SysVr3.0

In article <995@mcgill-vision.UUCP>, mouse@mcgill-vision.UUCP (der Mouse) writes:
 > > Last night in lab, I had about 12 users compiling small C programs
 > > [and "no space on disk 0 partition 0" messages started appearing].
 > > [/ was out of space, but some space appeared shortly thereafter.]
 > 
 > > I'm guessing that things are happening in /tmp, right?
 > 
 > Almost certainly.  Every UNIX C compiler I've seen uses /tmp to hold
 > intermediate results, and other programs do the same.  Circumstantial
 > evidence also indicates /tmp (the space hog vanished quickly, which
 > files in /tmp tend to do).

  Sun's version of cc has a switch which allows you to use pipes
instead of intermediate files - the "-pipe" option.


-- 

Eddie Wyatt 				e-mail: edw@ius1.cs.cmu.edu