Curt Sampson <cjs@cynic.net> writes:

> There's a trick you can use with sysctl to get the kernel to allocate
> a huge chunk of memory and deallocate it or something like that that
> will clear up the problem temporarially. I don't remember just what it
> is, though. It may have been something that forced a lot of stuff out
> to swap, and then de-allocated the memory. In fact, if I'm not entirely
> wrong, perhaps it was just a little C program that malloc'd between 0.5
> and 1 times your system ram, touched one byte on every page, and then
> exited.
>
> Anyone, someone should find it and document it in a FAQ somewhere. And
> then hack the kernel to use that to fix the problem. :-)

You mean like http://mail-index.netbsd.org/netbsd-users/2004/07/22/0001.html

/Johan