From owner-freebsd-questions  Tue Nov  4 12:55:13 1997
Return-Path: <owner-freebsd-questions>
Received: (from root@localhost)
          by hub.freebsd.org (8.8.7/8.8.7) id MAA06836
          for questions-outgoing; Tue, 4 Nov 1997 12:55:13 -0800 (PST)
          (envelope-from owner-freebsd-questions)
Received: from federation.addy.com (federation.addy.com [207.239.68.2])
          by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id MAA06821
          for <freebsd-questions@FreeBSD.ORG>; Tue, 4 Nov 1997 12:55:06 -0800 (PST)
          (envelope-from fbsdlist@federation.addy.com)
Received: from localhost (fbsdlist@localhost) by federation.addy.com (8.8.5/8.6.12) with SMTP id PAA09126 for <freebsd-questions@FreeBSD.ORG>; Tue, 4 Nov 1997 15:55:03 -0500 (EST)
Date: Tue, 4 Nov 1997 15:55:02 -0500 (EST)
From: Cliff Addy <fbsdlist@federation.addy.com>
To: freebsd-questions@FreeBSD.ORG
Subject: Preventing core dumps
Message-ID: <Pine.BSF.3.95q.971104155201.8532A-100000@federation.addy.com>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Sender: owner-freebsd-questions@FreeBSD.ORG
X-Loop: FreeBSD.org
Precedence: bulk

I seem to remember a way to do this, but can't seem to find it.  I
*thought* it was a kernel option, but apparently not.  I want the system
to *not* produce a core file on a crash.  I want our webserver to stop
dropping core files every time some users CGI script blows up.

BTW, I tried using the /etc/login.conf with coredumpsize=1M, but still
generate massive core files.

Cliff