On 08/30/14 06:03, Craig R. Skinner wrote:
Just an FYI;-
While preparing to wipe reinstall a box with a different partitioning
layout, I noticed these 2 items about /tmp space:
http://www.openbsd.org/faq/faq4.html#Partitioning
o /tmp: 50M is usually many times what you should ever need,
disklabel(8) AUTOMATIC DISK ALLOCATION
/tmp 8% of disk. 120M - 4G
Was there a point you are trying to make?
First of all, you did a stellar job of creative editing. Looking at the
FULL statement from the FAQ:
Most systems can get by with very modest amounts of storage here, 50M
is usually many times what you should ever need, though there are a few
applications which can use much, much more.
I don't see these at all in conflict.
A system running base applications usually uses very little /tmp space
-- it's important to have, but it is small stuff that goes there.
If you are creating your own partition structure, you can set it to the
size you need. Maybe on an older CF-based Soekris firewall, you devote
1MB of RAM to an MFS /tmp. If you are building big ports, maybe you
want gigabytes of /tmp. If you are running an internal CVS server and
don't bother to chroot it, you may not only want a lot of /tmp space,
but with the number of inodes cranked up. If you are letting the
installer make the decision, the installer is going to go big, to keep
you from whining when you want to use /tmp for something that wasn't
anticipated.
If you have great gobbs of disk space, go ahead, crank it up and use
/tmp for other things, use it for your own temporary storage space,
space for shuttling files between users, etc. By its nature, use of
/tmp can expand as space is available.
Nick.
