Path: csiph.com!x330-a1.tempe.blueboxinc.net!usenet.pasdenom.info!news.albasani.net!eternal-september.org!feeder.eternal-september.org!.POSTED!not-for-mail From: Tim Watts Newsgroups: comp.os.linux.misc Subject: Re: linux raid vs hw raid Followup-To: comp.os.linux.misc Date: Fri, 15 Apr 2011 07:22:32 +0100 Organization: A noiseless patient Spider Lines: 26 Message-ID: <3s4l78-6vi.ln1@squidward.dionic.net> References: <-NmdnSetarUCAzvQnZ2dnUVZ8hKdnZ2d@lyse.net> <35qeq61o56nifjseocj5jf7c3h1k6snjv8@4ax.com> Mime-Version: 1.0 Content-Type: text/plain; charset="ISO-8859-1" Content-Transfer-Encoding: 7Bit Injection-Info: mx02.eternal-september.org; posting-host="TAptT0I0+87//47GahNiQQ"; logging-data="23532"; mail-complaints-to="abuse@eternal-september.org"; posting-account="U2FsdGVkX1/InAeUGosCT6I3LMgogbcdAJ0AfCV/tw0=" User-Agent: KNode/4.4.6 Cancel-Lock: sha1:HXHgGSw9KUa2VWRyQfWBOjLOTkE= Xref: x330-a1.tempe.blueboxinc.net comp.os.linux.misc:747 Grant wrote: > On Thu, 14 Apr 2011 09:15:32 +0200, David Brown > Don't leave a saturated /tmp space! >> >>(Note that /var/tmp should really survive a reboot. However, I have >>never heard of any programs that actually rely on that - but no >>guarantees. /tmp should always be safe on tmpfs.) > > Hmm, I don't do anything special for /var/tmp, but on a slack-11.0 box > been up 16 days, it's empty. ON the 'pooh' box above, it's got old crap > surviving boot for KDE, 2.2MB for a single user, wonder why? I tend > towards wanting to flush that one on boot too, or make it in tmpfs. What I do is cron a find ... | xargs rm that kills off anything with an atime *and* mtime more than a few days old. It would work well enough for mtime alone if you have "notime" on. Cheers Tim -- Tim Watts