From owner-freebsd-questions Thu Dec 2 0:35: 3 1999 Delivered-To: freebsd-questions@freebsd.org Received: from axl.noc.iafrica.com (axl.noc.iafrica.com [196.31.1.175]) by hub.freebsd.org (Postfix) with ESMTP id 49C3814CC4 for ; Thu, 2 Dec 1999 00:34:57 -0800 (PST) (envelope-from sheldonh@axl.noc.iafrica.com) Received: from sheldonh (helo=axl.noc.iafrica.com) by axl.noc.iafrica.com with local-esmtp (Exim 3.040 #1) id 11tRgj-000Gec-00; Thu, 02 Dec 1999 10:34:05 +0200 From: Sheldon Hearn To: "Cheney Brothers, Inc." Cc: freebsd-questions@freebsd.org Subject: Re: Memory Leak In-reply-to: Your message of "Fri, 31 Dec 1999 12:52:45 EST." <01BF538D.F007CB40@MIKENEW> Date: Thu, 02 Dec 1999 10:34:05 +0200 Message-ID: <64021.944123645@axl.noc.iafrica.com> Sender: owner-freebsd-questions@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Fri, 31 Dec 1999 12:52:45 EST, "Cheney Brothers, Inc." wrote: > What happenes is Apache logs an error in the web server logs stating it = > can not spawn or run process because resourses are temrorarily = > unavailable. If I reboot and have the free extra memory free the cgi = > will run fine. If this was caused by memory shortage, you'd see "out of swap" errors in /var/log/messages. I suggest you post the exact error message that you see in the Apache logs so that we can hunt it down in the Apache source. However, I'm willing to bet that you're using an old release of FreeBSD for which login.conf sets restrictions on the number of child processes and amount of memory any process can use _by_ _default_. Modern releases of FreeBSD don't impose these per-process limits by default. Have a look at /etc/login.conf and you'll probably find that the default class is restricted. Ciao, Sheldon. PS: Keep freebsd-questions in the loop when you send follow-up so that others can benefit from this correspondance. :-) To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-questions" in the body of the message