Rob van der Heij wrote:
On Tue, Mar 18, 2008 at 5:18 AM, Mark Post <[EMAIL PROTECTED]> wrote:
As others have talked about, real storage in a shared environment is something
to be used wisely. If you don't have a need for a blazingly fast /tmp file
system, you might be better off with either real DASD, or VDISK space (assuming
you have z/VM). If you like the idea of /tmp being completely cleaned out with
every system boot, there's nothing stopping you from doing that in a local
startup script. The Filesystem Hierarchy Standard explicitly states that the
contents of /tmp are not guaranteed to be preserved across a reboot.
I assume we're talking Linux on z/VM. For Linux in LPAR or on
otherwise dedicated hardware, I don't care what you do with memory.
Nobody else can use what you don't need (unless you're using /tmp as
motivation to make all Linux LPARs 8GB or so).
The "normal" usage of Linux in /tmp is pretty limited, so I don't
think I'd be scared about a few MBs there. But since those files
probably remain in page cache while you need them, you do not win
anything there. But I have also seen sysadmins use /tmp to hold big
files that did not fit in /root anymore. Or when you build packages
the scripts may use /tmp to build the data. In that case I would
rather not do it in memory. Eventually things need to be paged and
your actual disk space requirements will be more than double.
rpm uses /var/tmp (I wish it used /tmp, but never mind). I think gcc
uses /tmp.
I think it's sound if
1. You're on real hardware
2. You manage the possibility of excessively large files there causing
grief. Bear in mind that managing _that_ might cause grief in another
direction.
3. You actually use /tmp enough to make it worth the trouble. Mounting
/tmp on another volume would allow this to be measured, I don't know
what options for measurement exist otherwise.
But z/VM offers you other options. You might be able to use T-disk to
satisfy your temporary requirements for disk space. Or you might be
able to mount the data via NFS and maybe avoid the duplication of
data.
I'd not share /tmp with other systems.
--
Cheers
John
-- spambait
[EMAIL PROTECTED] [EMAIL PROTECTED]
-- Advice
http://webfoot.com/advice/email.top.php
http://www.catb.org/~esr/faqs/smart-questions.html
http://support.microsoft.com/kb/555375
You cannot reply off-list:-)
----------------------------------------------------------------------
For LINUX-390 subscribe / signoff / archive access instructions,
send email to [EMAIL PROTECTED] with the message: INFO LINUX-390 or visit
http://www.marist.edu/htbin/wlvindex?LINUX-390
