From owner-freebsd-questions  Wed Feb 19 18:27:51 1997
Return-Path: <owner-questions>
Received: (from root@localhost)
          by freefall.freebsd.org (8.8.5/8.8.5) id SAA07485
          for questions-outgoing; Wed, 19 Feb 1997 18:27:51 -0800 (PST)
Received: from gdi.uoregon.edu (gdi.uoregon.edu [128.223.170.30])
          by freefall.freebsd.org (8.8.5/8.8.5) with ESMTP id SAA07479
          for <freebsd-questions@freebsd.org>; Wed, 19 Feb 1997 18:27:44 -0800 (PST)
Received: from localhost (dwhite@localhost) by gdi.uoregon.edu (8.8.5/8.6.12) with SMTP id SAA14025; Wed, 19 Feb 1997 18:27:23 -0800 (PST)
Date: Wed, 19 Feb 1997 18:27:23 -0800 (PST)
From: Doug White <dwhite@gdi.uoregon.edu>
X-Sender: dwhite@localhost
Reply-To: Doug White <dwhite@resnet.uoregon.edu>
To: Victor Rotanov <vitjok@fasts.com>
cc: freebsd-questions@freebsd.org
Subject: Re: coredumps
In-Reply-To: <199702191722.JAA04375@freefall.freebsd.org>
Message-ID: <Pine.BSI.3.94.970219182639.13952E-100000@localhost>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Sender: owner-questions@freebsd.org
X-Loop: FreeBSD.org
Precedence: bulk

On Wed, 19 Feb 1997, Victor Rotanov wrote:

> How can i disable coredumps so that they cannot be re-enabled?

Disabling them is easy, for csh-variants put 'set coredumpsize 0' into
your .cshrc.  

Making that systemwide permanent, that is more difficult, w/o hacking the
kernel.  AFAIK.

Doug White                              | University of Oregon  
Internet:  dwhite@resnet.uoregon.edu    | Residence Networking Assistant
http://gladstone.uoregon.edu/~dwhite    | Computer Science Major