From owner-freebsd-questions Mon Sep 22 05:58:07 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id FAA10604 for questions-outgoing; Mon, 22 Sep 1997 05:58:07 -0700 (PDT) Received: from keywest.ird.rl.af.mil (KEYWEST.IRD.RL.AF.MIL [128.132.193.224]) by hub.freebsd.org (8.8.7/8.8.7) with SMTP id FAA10585 for ; Mon, 22 Sep 1997 05:58:02 -0700 (PDT) Received: by keywest.ird.rl.af.mil with Microsoft Exchange (IMC 4.0.837.3) id <01BCC735.F59D4490@keywest.ird.rl.af.mil>; Mon, 22 Sep 1997 09:00:22 -0400 Message-ID: From: "Goeringer, Michael" To: "'Steve Hovey'" Cc: "'freebsd-questions@freebsd.org'" Subject: RE: capping forks Date: Mon, 22 Sep 1997 09:00:20 -0400 X-Mailer: Microsoft Exchange Server Internet Mail Connector Version 4.0.837.3 MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Sender: owner-freebsd-questions@freebsd.org X-Loop: FreeBSD.org Precedence: bulk In the kernel you can set CHILD_MAX=. Ofcourse this affects the entire system so Doug may have a better solution. Michael G. ---------- From: Steve Hovey[SMTP:shovey@buffnet.net] Sent: Thursday, September 18, 1997 9:36 PM To: freebsd-questions@FreeBSD.ORG Subject: capping forks How does one safely limit the number of child processes a program can fork? The old smtp mailer I used did this fine, but smap does not and occational spam attacks have made problems. I compared source and they seem to use the same method but Im not up enough on this to be sure. Any ideas appreciated!