From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: zsh-workers-request@euclid.skiles.gatech.edu Received: from euclid.skiles.gatech.edu (list@euclid.skiles.gatech.edu [130.207.146.50]) by coral.primenet.com.au (8.7.6/8.7.3) with ESMTP id GAA04890 for ; Sat, 16 Nov 1996 06:56:13 +1100 (EST) Received: (from list@localhost) by euclid.skiles.gatech.edu (8.7.3/8.7.3) id OAA27144; Fri, 15 Nov 1996 14:54:00 -0500 (EST) Resent-Date: Fri, 15 Nov 1996 14:38:42 -0500 (EST) Message-Id: <199611151939.OAA15731@nerc3.nerc.com> Content-Type: text/plain MIME-Version: 1.0 (NeXT Mail 3.3 v118.2) X-Image-URL: http://www.nerc.com/~luomat/Timothy_J_Luoma-X-Face.tiff X-Nextstep-Mailer: Mail 3.3 (Enhance 2.0b5) From: Timothy J Luoma Date: Fri, 15 Nov 96 14:38:47 -0500 To: zsh-users@math.gatech.edu Subject: limit coredumpsize 0 not working on 3.0.0 Organization: Princeton Theological Seminary Resent-Message-ID: <"wXpR11.0.UY6.2RCZo"@euclid> Resent-From: zsh-users@math.gatech.edu X-Mailing-List: archive/latest/506 X-Loop: zsh-users@math.gatech.edu X-Loop: zsh-workers@math.gatech.edu Precedence: list Resent-Sender: zsh-workers-request@math.gatech.edu I've found several large "core" files on my SunOS account with zsh 3.0.0, even though I have limit coredumpsize 0 in .zshenv. What should I be doing to prevent this? TjL