James Hofmeister wrote:

> The most common/frequent cause for a fork to fail in inetd is a resource
> error, typically "out of disk space" or "out of contiguous disk space".

History repeats itself :-)

I wrote on Mon, 30 Dec 1996 18:45:18 -0500:

> The more serious problem was with posix fork().  To perform a fork(),
> the parent's data space is "cloned" by a special VSM internal routine.
> This routine requires a contiguous extent of transient space on the same
> ldev as the parent.  If there isn't adequate contiguous space, rather
> than looking elsewhere, it initially aborted the parent; there was
> "patch" which changes this to a EAGAIN error from fork() [resource busy,
> try again].  But to my knowledge, neither the ldev 1 "conservative
> allocation feature" nor the VSM cloning routine has been touched through
> 5.5 powerpatch 1.

http://raven.utc.edu/cgi-bin/WA.EXE?A2=ind9612E&L=hp3000-l&P=R806

Jeff

* To join/leave the list, search archives, change list settings, *
* etc., please visit http://raven.utc.edu/archives/hp3000-l.html *