Tight Memory Kludge in USG 3B2 5.3

[John Kullmann]

Since switching from 5.2.2 to 5.3 we've noticed frequent
console messages like:
  ptalloc - Insufficient memory to allocate %d pages - system call failed

Where 5.2.2 would sleep at various places along the fork() path,
5.3 has all this NOSLEEP nonsense, returns EAGAIN(!!) and fails. 
Basically, if you do not have enough free memory to dup all the private
regions of your process (see procdup()/dupreg()) under 5.3 you are out of luck. 
This is a major change from 5.2 and one that doesn't seem beneficial.

Anyone else running into this? Anyone understand this? Anyone
justify this? Anyone have a fix for this??

John Kullmann
opus systems
..!{sun,pyramid,hplabs}!opusys!jk