In message <18453.815621505@BALVENIE.PDL.CS.CMU.EDU>you write:
> > > I think this problem is real, considering the number of people who have
> > > reported it.
> > 
> > It certainly is real. It's an old problem in the VM code.
> 
> And, unless i'm mistaken, it was one of the first problems that the
> FreeBSD folks fixed in their VM code.  (Granted the fix was a hack...
> but which is better: "hacked" or "broken"?)

Maybe they fixed this one, but I like it better the way it works in NetBSD, 
than in FreeBSD 2.x which crashes our machine up to twice a day ...

> The problem usually shows itself when you have a long-running server
> process on a highly-loaded machine.  When the server forks to exec a
> new program (for example), if it pages before the child has exec'd,
> then swap space will typically be 'lost' until the the parent exits.

If you add enough memory, problems will not show up excessively which maybe 
why it was never noticed by me.

Gruesse
       Oskar

 ==============================================================================
 					Tragbar ist, was nicht herunterfaellt.
						    oskar@zappa.unna.ping.de
 ==============================================================================