On Tue, 1 Jul 2003, Cliff Woolley wrote: > don't use it. We intentionally do not check for OOM conditions because, > though we've had many heated debates about this, we've always arrived at > the consensus that if you hit OOM, your box is hosed anyway and virtually > any effort you make to correct it other than dying will just make things
Never tried this with 2.0; but with 1.3 I've regularly used loging.conf/ulimits to manage footprint; and relied on getting a child emit an early "Ouch! Out of memory!" followed by its exit(1) bail to amke sure things did not spin out of control and hose the box. Dw
