Return to BSD News archive
Xref: sserve comp.os.386bsd.questions:12468 comp.os.386bsd.misc:3267 Path: sserve!newshost.anu.edu.au!harbinger.cc.monash.edu.au!bunyip.cc.uq.oz.au!munnari.oz.au!ihnp4.ucsd.edu!agate!biosci!headwall.Stanford.EDU!leland.Stanford.EDU!yergeau From: yergeau@leland.Stanford.EDU (Dan Yergeau) Newsgroups: comp.os.386bsd.questions,comp.os.386bsd.misc Subject: Disk activity when compiling (was Re: Whats wrong with Linux networking ??? ) Date: 18 Aug 1994 17:38:49 GMT Organization: DSG, Stanford University, CA 94305, USA Lines: 17 Distribution: world Message-ID: <3306b9$502@nntp2.Stanford.EDU> References: <1994Aug15.034939.20997@cs.brown.edu> <32te9lINN6ab@bonnie.sax.de> NNTP-Posting-Host: elaine24.stanford.edu In article <32te9lINN6ab@bonnie.sax.de>, j@uriah.sax.de (J Wunsch) writes: |> mhw@cs.brown.edu (Mark Weaver) writes: |> |> >disk activity. I always get significant disk activity from compiling, |> >even though my /tmp is a ramdisk. |> Are you sure your temp files go via the ramdisk? If I'm not mistaken, on FreeBSD, cc's temp files go to either /usr/tmp or /var/tmp, not /tmp. You should 'setenv TMPDIR /tmp' to get them to go to the MFS/ramdisk partition. -- Dan Yergeau You are in a twisty little passage yergeau@gloworm.Stanford.EDU of standards, all conflicting. #include <std.disclaimer>