Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP
Path: utzoo!mnetor!seismo!lll-crg!nike!oliveb!bene!opusys!jk
From: jk@opusys.UUCP (John Kullmann)
Newsgroups: net.unix-wizards
Subject: Tight Memory Kludge in USG 3B2 5.3
Message-ID: <141@opusys.UUCP>
Date: Fri, 5-Sep-86 15:41:51 EDT
Article-I.D.: opusys.141
Posted: Fri Sep  5 15:41:51 1986
Date-Received: Sat, 6-Sep-86 05:35:23 EDT
Organization: Opus Systems, Cupertino, CA
Lines: 16
Keywords: kludge, 5.3, memory

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