In message <CoFnzu.LnJ@endicor.com>, Ty Sarna writes:
>In article <199404180056.KAA13179@nutmeg> Arthur Hoffmann <hoffmann@it.ntu.edu
>.au> writes:
>> Hi, 
>> I found that whenever I used my /tmp directory heavily the swap
>> space got recduced. Now, after I cleared the /tmp directory again the
>> swapspace doesn't increase anymore. Is there any way to let the system
>> know that the free /tmp (mfs) space is usable for vm again?
>
>Not with the current mfs, It would need a lot of work to be able to
>release VM to the system. mfs is *NOT* like SunOS tmpfs.
>
>Also note that by default mfs uses as much memory as the partition you
>mount it on! If you only have one swap partition, DON'T MOUNT MFS ON IT
>WITHOUT USING THE -s FLAG TO LIMIT THE AMOUNT OF SWAP MFS USES!!!
>If you don't use -s bad things can happen.

This suggestion interests me, as I find that gcc compiles lock the
system in direct proportion to the amount of current activity (running
apps).  Without forcing a huge explanation of the mfs internals
(although that would be interesting) can you explain what's going on?
Most NetBSD implementations that I've seen simply include a line such
as:

/dev/sd1b               /tmp    mfs     rw      1       1

in their /etc/fstab.  Is this incorrect for a system with only one
swap partition?

FYI, my system is a 33MHz '030/882 with 8M 32bit mem and a 30Mb swap
partition, with mfs mounted on it via the line shown above.

Thanks.

---
Bill Squier (groo@menger.eecs.stevens-tech.edu)
"If you can read this, you're too close"

------------------------------------------------------------------------------