From owner-freebsd-hackers  Mon Aug 10 03:21:26 1998
Return-Path: <owner-freebsd-hackers@FreeBSD.ORG>
Received: (from majordom@localhost)
          by hub.freebsd.org (8.8.8/8.8.8) id DAA16570
          for freebsd-hackers-outgoing; Mon, 10 Aug 1998 03:21:26 -0700 (PDT)
          (envelope-from owner-freebsd-hackers@FreeBSD.ORG)
Received: from verdi.nethelp.no (verdi.nethelp.no [158.36.41.162])
          by hub.freebsd.org (8.8.8/8.8.8) with SMTP id DAA16548
          for <hackers@FreeBSD.ORG>; Mon, 10 Aug 1998 03:21:21 -0700 (PDT)
          (envelope-from sthaug@nethelp.no)
From: sthaug@nethelp.no
Received: (qmail 18041 invoked by uid 1001); 10 Aug 1998 10:20:53 +0000 (GMT)
To: hasty@rah.star-gate.com
Cc: hackers@FreeBSD.ORG
Subject: Re: can not fork...
In-Reply-To: Your message of "Mon, 10 Aug 1998 02:03:04 -0700"
References: <199808100903.CAA04280@rah.star-gate.com>
X-Mailer: Mew version 1.05+ on Emacs 19.34.2
Mime-Version: 1.0
Content-Type: Text/Plain; charset=us-ascii
Date: Mon, 10 Aug 1998 12:20:53 +0200
Message-ID: <18039.902744453@verdi.nethelp.no>
Sender: owner-freebsd-hackers@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG

> Plenty of swap space:
> {hasty} swapinfo
> Device      512-blocks     Used    Avail Capacity  Type
> /dev/sd0s1b     262144    94096   167792    36%    Interleaved
> {hasty} sysctl kern.maxproc
> kern.maxproc: 500

You haven't given enough info - you could still be bumping against
login.conf limits.

I ended up having to increase maxproc-cur for the "root" and "default"
entries quite a bit, on a 2.2.6 system.

Steinar Haug, Nethelp consulting, sthaug@nethelp.no

To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-hackers" in the body of the message