The /tmp mountpoint is a filesystem built on free swapspace from the operating
system. The amount of "kbytes" represents the amount of free swapspace, thus
as swap is used and freed from the system, this column will change for the /tmp
filesystem. When you create files in /tmp, you allocate out of the free swap
area. Thus, if you use up all of /tmp with files, your machine will have
no swap space left. All swapfiles, raw partitions allocated for swap, etc
boil into 1 number for both the total virtual space available, and thus for the
amount of space usable by /tmp. If you keep on running out of swap, you
may want to see if anything is generating large files to /tmp.
Scott
--------------------------------------------------------------------------- > in a standard installation for Solaris 2.4, it suggests for > Sometimes he runs out of swap and occasionally even REBOOTING. > Ok this works. But I was wondering wether the system will fill the > I was wondering about an option to say which swap comes first. Maybe > Also I find it very strange that the system runs out of memory > Last but not least: > Thanks for the reply > Patrick.
Real Time Enterprises | Scott MacKay
Pittsford,NY 14534 | Real Time Enterprises
- Electronic Document Imaging - System Integration - | (716) 383-1290
- Software Development- | Postmaster
---------------------------------------------------------------------------
> Hello,
> a 16M system a 32 swap space. This one is located on /dev/dsk/c0t3d0s1
> as is the default.
> What I've done is to allocate extra swap via the following commands:
> mkfile 20m /extraswap
> swap -a /extraswap
> default swap. Because this means that the /tmp which is mounted
> at boottime will fill up also.
> by changing the order in vfstab.
> with only openwindows running.
> when you perform a df -k and you look at the /tmp
> it changes . Is there a correlation between the space free on the tmp
> and the swap it takes?