Xref: utzoo comp.unix.questions:5985 comp.sys.att:2719
Path: utzoo!utgpu!water!watmath!clyde!att-cb!gwspc!n8emr!osu-cis!tut.cis.ohio-state.edu!mailrus!umix!uunet!mcvax!ukc!stc!ist!uel!olgb1!olapw
From: olapw@olgb1.oliv.co.uk (Tony Walton)
Newsgroups: comp.unix.questions,comp.sys.att
Subject: Re: NO SPACE  Error message
Summary: Temp directory is alterable
Keywords: 3b2/400, SysVr3.0
Message-ID: <428@olgb1.oliv.co.uk>
Date: 1 Mar 88 17:30:05 GMT
References: <225@mccc.UUCP> <1733@rtech.UUCP>
Organization: British Olivetti Ltd.,OEM/VAR Division, London, England.
Lines: 19

In article <1733@rtech.UUCP>, russ@llama.rtech.UUCP (Russ Spence) writes:
> In article <225@mccc.UUCP> pjh@mccc.UUCP (Peter J. Holsberg) writes:
> >Last night in lab, I had about 12 users compiling small C programs --
> >maybe 30 lines each --, and I started to get "no space on disk 0
> >
> 	/tmp is used by the compiler to store temporary files...
...

If you're using the AT&T Issue 4.1 (possibly Issue 3.0 as well, I can't
remember) you can set the TMPDIR environment variable to some directory
where there's space. Use the # option to cc to see where the beast is
putting its temporary files - if you set TMPDIR=/usr/tmp and export
TMPDIR, and cc still puts its files in /tmp it's not going to work and
you'll have to either expand root or put /tmp on a separate filesystem.
-- 
Tony Walton, OEM/VAR Division, British Olivetti Ltd., Wellington House,
154-160 Upper Richmond Road, London, England SW15 2FN
LONDON, SW15 2FN.  Tel: (+44) 1 789 6699 Telefax: (+44) 1 785 6670 Telex:27258
Uucp : { ukc | mcvax!olnl1 | ihnp4!cuuxb | iconet | olhqma } !olgb1!olapw