Subject: Re: can't fork but what's short?
To: der Mouse <mouse@Collatz.McRCIM.McGill.EDU>
From: Simon J. Gerraty <email@example.com>
Date: 04/11/1995 09:13:40
> > [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.
That was my brain failing.
> Number 5 also looks odd; I thought forking produced multiple pointers
> to single file table slots. Perhaps my memory is too faded.
More likely mine.
Anyway it was number 2. Trouble was that csh seems to be the only
thing that can tell you (apart from the source) what that limit was,
and I haven't used csh for years so forgot about it.