texanpenguin said:
I'm not 100-percent sure, but I would imagine that OSX gives other files permission to write over HDD space currently filled with SWAP data, meaning regardless how much HDD space it occupies, it's not going to prevent you from using that disk?
In OS X, a file is a file is a file, or it may be a folder -- but that is another story. Like any other file, Swapfiles are registered in the volume directory and data blocks used by a swapfile are inviolate. In other words, your imagination is 100%
wrong.
arri said:
but aren't all these mac-(+other unix) users so proud of uptimes exceeding weeks or even months?
Swapfiles can be reused so just because at one time you were editing a 2 GB file in Photoshop, a 600 page Word document, and 100 Page InDesign document all at the same time, and the system had to create 3 GB of swapfile space to accommodate all that doesn't mean that an additional swapfiles will be created the next time you are doing some that takes a lot of swapfile space. The system will simply reuse the swapfiles that are already there. And yes it might be a nice feature if OS X would "recover" the swapfile space after some interval. By-the-way, I am one of those users you are talking about.
DeltaMac said:
Some say it's risky to delete swap files on a running system, but I don't know.
Look at it this way, if the swapfile is currently being used when you delete it you will, at the very least, lose the data you were working with and at the other extreme could crash the entire system. On the other hand, OS X will not permit any currently open file to be deleted so either eventuality is highly unlikely.
arri said:
in crisis-times the os sometimes warns me that the boot volume is almost full, and the whole machines just hangs for some time..
The rule of thumb, based on extensive independent testing, for HFS+ [a.k.a Mac OS (Extended)] volumes is they should
never fall below 15% free space, regardless of how big or how little the drive is. When you fall below that rule of thumb there is a substantial risk of an irreparable "Overlapped Extents Allocation" error that not even DiskWarrior or TechTool Pro can fix. That is a function of how the HFS+ file system works and is independent of the operating system or applications. The risk is increased by the number of temporary cache, swap, and other temporary files used by OS X and OS X applications as well as OS X's tendency to fragment a drive.
arri said:
will tiger do a better job here?
We will find out, probably sometime in the late October or November time frame. Certainly Panther has made major improvements in virtual memory management and efficiency over Jaguar.