🚀 go-pugleaf

In article <1992Sep7.215151.2517@metrosoft.com> gvh@metrosoft.com (Gordon  
Van Huizen) writes:
> In article <1992Sep7.041747.10597@ccsun7.csie.nctu.edu.tw>  
> jypai@ccnext.csie.nctu.edu.tw writes:
> > I ran Movie.
> > then I found I was  running out of disk space.
> > So I checked /private/vm/swapfile with 'ls -l', and found:
> > 
> > -rw------t  1 root     44195840 Sep  7 12:12 swapfile
> > 
> > Obviously the swapfile eat up my disk space.

The swapfile not only cannot shrink, it cannot reuse space in
the file expanded for another app: It uses what space it can 
in the 1st 20meg, then creates a new expansion region for the 
currently running app.

Overall, it keeps expanding when more is needed by the app, even 
if the file is 100 megabytes! This is why, should the swapfile
expand, it expands to such great sizes (you'd think 100 meg
would be enough for almost anything...).

This can be demonstrated easily by running an app which
increases the swapfile, killing the app, and running it
again. You'll see the swapfile grow every time:

 swapfile     110372510  Sep 09 15:15  -rw------   1  root  wheel

This is a HUGE bug that NeXT apparently still hasn't addressed,
even in 3.0.  When you have to reboot your file server every couple 
of days, it gets old quickly.  This is just plain poor design.