From owner-freebsd-questions Sun Dec 13 08:18:12 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id IAA12890 for freebsd-questions-outgoing; Sun, 13 Dec 1998 08:18:12 -0800 (PST) (envelope-from owner-freebsd-questions@FreeBSD.ORG) Received: from scientia.demon.co.uk (scientia.demon.co.uk [212.228.14.13]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id IAA12875 for ; Sun, 13 Dec 1998 08:18:09 -0800 (PST) (envelope-from ben@scientia.demon.co.uk) Received: from ben by scientia.demon.co.uk with local (Exim 2.054 #18) id 0zpCzm-0002qR-00; Sun, 13 Dec 1998 14:59:42 +0000 Date: Sun, 13 Dec 1998 14:59:42 +0000 From: Ben Smithurst To: Sue Blake Cc: freebsd-questions@FreeBSD.ORG Subject: Re: cannot fork Message-ID: <19981213145942.D10841@scientia.demon.co.uk> References: <19981213211314.57505@welearn.com.au> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.95i In-Reply-To: <19981213211314.57505@welearn.com.au> Sender: owner-freebsd-questions@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Sue Blake wrote: > 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. How many processes do you have running, and how many is the maximum (according to `limits'[1])? If there is a large difference I have no idea. Perhaps you need to rebuild your kernel to allow more processes; I have maxusers=64 (which gives 2k processes, I'm allowed 1k by login.conf) with no problems. [1] sysctl kern.maxproc may also help of course, but you may be allowed less than the system limit -- Ben Smithurst ben@scientia.demon.co.uk send a blank message to ben+pgp@scientia.demon.co.uk for PGP key To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-questions" in the body of the message