HP3000-L Archives

August 1999, Week 4

HP3000-L@RAVEN.UTC.EDU
Options: Use Monospaced Font
Show Text Part by Default
Show All Mail Headers

Message: [<< First] [< Prev] [Next >] [Last >>]
Topic: [<< First] [< Prev] [Next >] [Last >>]
Author: [<< First] [< Prev] [Next >] [Last >>]

Print Reply
Subject:
Re: POSIX error msg: "cannot fork"
From:
Jeff Kell <[log in to unmask]>
Reply To:
Jeff Kell <[log in to unmask]>
Date:
Wed, 25 Aug 1999 00:11:23 -0400
Content-Type:
text/plain
Parts/Attachments:
text/plain (19 lines) 
Bob Hemmer wrote:
>
> I'm working with a unix programmer trying to run programs in the POSIX
> shell.   We keep getting the following error:
>
> /etc/profile 64: tput: cannot fork: Resource busy, try again
> /etc/profile 64: tput: Internal error: j_close: no processes
> shell/iX> vi jj
> vi: cannot fork: Resource busy, try again
> vi: Internal error: j_close: no processes
>
> what corrective action should we take?

Defrag your system volume set, this is a long-standing issue/problem
with fork().  You must have "lots" of contiguous free space available to
transient space on each and every system volume.

Jeff Kell <[log in to unmask]>

ATOM RSS1 RSS2