Subject: Re: can't fork but what's short?
To: None <current-users@NetBSD.ORG>
From: der Mouse <mouse@Collatz.McRCIM.McGill.EDU>
Date: 04/10/1995 13:29:20
> [W]hen a fork fails, its normally:
> 1/ out of process table slots
> 2/ exceeded # procs per user
> 3/ out of swap
> 4/ out of pty's
> 5/ file table full
> 6/ page translation tables
What's with number 4? Forking doesn't require a pty last I knew.
Number 5 also looks odd; I thought forking produced multiple pointers
to single file table slots. Perhaps my memory is too faded.