From mboxrd@z Thu Jan  1 00:00:00 1970
Return-Path: <zsh-workers-return-9647-mason-zsh=primenet.com.au@sunsite.auc.dk>
Received: (qmail 20820 invoked from network); 10 Feb 2000 10:02:44 -0000
Received: from sunsite.auc.dk (130.225.51.30)
  by ns1.primenet.com.au with SMTP; 10 Feb 2000 10:02:44 -0000
Received: (qmail 27373 invoked by alias); 10 Feb 2000 10:02:35 -0000
Mailing-List: contact zsh-workers-help@sunsite.auc.dk; run by ezmlm
Precedence: bulk
X-No-Archive: yes
X-Seq: 9647
Received: (qmail 27366 invoked from network); 10 Feb 2000 10:02:34 -0000
Subject: Re: RLIM_NLIMITS compile problem
In-Reply-To: <1000209180231.ZM1102@candle.brasslantern.com> from Bart Schaefer
 at "Feb 9, 2000 06:02:31 pm"
To: Bart Schaefer <schaefer@candle.brasslantern.com>
Date: Thu, 10 Feb 2000 10:02:25 +0000 (GMT)
CC: Adam Spiers <adam@spiers.net>, 
 zsh workers mailing list <zsh-workers@sunsite.auc.dk>
X-Mailer: ELM [version 2.4ME+ PL66 (25)]
MIME-Version: 1.0
Content-Type: text/plain; charset=US-ASCII
Content-Transfer-Encoding: 7bit
Message-Id: <E12IqQb-0003gY-00@crucigera.fysh.org>
From: Zefram <zefram@fysh.org>

Bart Schaefer wrote:
>So I'm puzzled, but:  Zefram et al., what's the reason that those
>HAVE_GETRLIMIT bits in exec.c were never moved to the rlimits module?

Only the builtins were moved.  Looking at it, it appears that all the
resource limit handling code could reasonably be moved into the module,
using hooks, since if the limit-setting builtins are never used then
the limit setting is a no-op.

-zefram