From mboxrd@z Thu Jan  1 00:00:00 1970
Return-Path: <zsh-users-return-4957-mason-zsh=primenet.com.au@sunsite.dk>
Received: (qmail 24096 invoked from network); 10 May 2002 21:39:14 -0000
Received: from sunsite.dk (130.225.247.90)
  by ns1.primenet.com.au with SMTP; 10 May 2002 21:39:14 -0000
Received: (qmail 15461 invoked by alias); 10 May 2002 21:39:00 -0000
Mailing-List: contact zsh-users-help@sunsite.dk; run by ezmlm
Precedence: bulk
X-No-Archive: yes
X-Seq: 4957
Received: (qmail 15448 invoked from network); 10 May 2002 21:38:58 -0000
Date: Fri, 10 May 2002 14:38:50 -0700 (PDT)
From: Bart Schaefer <schaefer@brasslantern.com>
Sender: schaefer@ns1.sodaware.com
To: Thorsten Haude <zsh@thorstenhau.de>
cc: Zsh users list <zsh-users@sunsite.dk>
Subject: Re: umlimit and /etc/zshenv
In-Reply-To: <20020510212027.GP1124@eumel.yoo.net>
Message-ID: <Pine.LNX.4.44.0205101433270.12406-100000@ns1.sodaware.com>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII

On Fri, 10 May 2002, Thorsten Haude wrote:

> I want to explore the issue to find the best way of dealing with this.

The best thing would be for mutt to either use soft limits, or restore the
old limit (which I don't think is possible with hard limits anyway).

The second-best thing would be for you to use something like

[ -t 2 ] && ulimit -c ...

so that the command executes only when somebody might actuall see the
error output.