From owner-freebsd-questions Sun Dec 13 02:13:30 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id CAA08567 for freebsd-questions-outgoing; Sun, 13 Dec 1998 02:13:30 -0800 (PST) (envelope-from owner-freebsd-questions@FreeBSD.ORG) Received: from phoenix.welearn.com.au (suebla.lnk.telstra.net [139.130.44.81]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id CAA08562 for ; Sun, 13 Dec 1998 02:13:26 -0800 (PST) (envelope-from sue@phoenix.welearn.com.au) Received: (from sue@localhost) by phoenix.welearn.com.au (8.9.1/8.9.0) id VAA07207; Sun, 13 Dec 1998 21:13:20 +1100 (EST) Message-ID: <19981213211314.57505@welearn.com.au> Date: Sun, 13 Dec 1998 21:13:14 +1100 From: Sue Blake To: freebsd-questions@FreeBSD.ORG Subject: cannot fork Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.88e Sender: owner-freebsd-questions@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I'm getting variations on the cannot fork message when trying to view man pages from an xterm. xman isn't very happy either. This is 2.2.6-STABLE in case it matters. Other programs will run without complaint. If I close a few xterms, man will start working too. I know it's been asked before, the mail archives are full of the question but I can't find the posts containing the answers. I thought it might be common enough to get FAQ status, but no. Here's a taste: sue@vedanix$ man ls Cannot fork Error executing formatting or display command. system command exited with status 512 No manual entry for ls sue@vedanix$ man man Formatting page, please wait...Cannot fork Failed. Error executing formatting or display command. system command exited with status 512 Cannot fork Error executing formatting or display command. system command exited with status 512 No manual entry for man sue@vedanix$ apropos ls /usr/bin/apropos: Cannot fork apropos: manpath is null, use "/usr/share/man" /usr/bin/apropos: Cannot fork /usr/bin/apropos: Cannot fork -- Regards, -*Sue*- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-questions" in the body of the message