Date: Mon, 14 Dec 1998 06:54:51 +0100 (CET) From: List User <listuser@netspace.net.au> To: freebsd-questions@FreeBSD.ORG Message-ID: <199812140554.GAA07895@doorway.home.lan>
next in thread | raw e-mail | index | archive | help
Newsgroups: freebsd.questions Path: root From: Ben Smithurst <ben@scientia.demon.co.uk> Subject: Re: cannot fork Content-Type: text/plain; charset=us-ascii Received: from ben by scientia.demon.co.uk with local (Exim 2.054 #18) id 0zpIKe-0004gK-00; Sun, 13 Dec 1998 20:41:36 +0000 To: Sue Blake <sue> Sender: owner-freebsd-questions@FreeBSD.ORG Organization: Private News Host Precedence: bulk Message-ID: <19981213204136.A17472@scientia.demon.co.uk> X-Mailer: Mutt 0.95i References: <19981213211314.57505@welearn.com.au> <19981213145942.D10841@scientia.demon.co.uk> <19981214070131.32240@welearn.com.au> Delivered-To: vmailer-questions@freebsd.org X-Uidl: a6ebc0001149047c3b98b5c7afcd3ffe X-Loop: FreeBSD.ORG Mime-Version: 1.0 In-Reply-To: <19981214070131.32240@welearn.com.au> Cc: freebsd-questions Date: Sun, 13 Dec 1998 20:41:36 GMT Sue Blake wrote: > Thanks Ben, it sounds like you're on the right track here even though > I understand ver little of what you've said. Could you translate some > of it into "do this" style? > > I get that 'limits' is a command I can type, and it comes back with > maxprocesses-cur 64 What does $ sysctl kern.maxproc show? That's the system wide limit, which may be higher than your user limit. I'm guessing that while you're running X you could easily get 64 processes. (`ps ax | wc -l' will tell you how many procs you have, near enough anyway.) If kern.maxproc is a lot higher than 64, you can probably just alter some settings in /etc/login.conf to increase the per-user limits (following the instructions at the top of login.conf about rebuilding the database). To find out which class you are in, do `limits -U sue', or something: $ limits -U ben Resource limits for class staff: shows I'm in the `staff' class. You can change your class if needed using vipw, it's the fifth field along (which may well be blank, and can safely be left blank). If kern.maxproc isn't much higher, rebuild your kernel, replacing the maxusers line in the kernel config file with maxusers 64 or some such value. Reboot, check kern.maxproc and your limits, and see if things are working better. -- 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 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-questions" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?199812140554.GAA07895>