From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from euclid.skiles.gatech.edu (list@euclid.skiles.gatech.edu [130.207.146.50]) by melb.werple.net.au (8.7.5/8.7.3/2) with ESMTP id EAA12955 for ; Sun, 30 Jun 1996 04:17:24 +1000 (EST) Received: (from list@localhost) by euclid.skiles.gatech.edu (8.7.3/8.7.3) id OAA22843; Sat, 29 Jun 1996 14:12:02 -0400 (EDT) Resent-Date: Sat, 29 Jun 1996 14:12:02 -0400 (EDT) From: Zoltan Hidvegi Message-Id: <199606291553.RAA02304@hzoli.ppp.cs.elte.hu> Subject: ulimit should limit the shell? To: zsh-workers@math.gatech.edu (Zsh hacking and development) Date: Sat, 29 Jun 1996 17:53:30 +0200 (MET DST) X-Mailer: ELM [version 2.4ME+ PL17 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Resent-Message-ID: <"EiaKm2.0.ra5.n7Nrn"@euclid> Resent-From: zsh-workers@math.gatech.edu X-Mailing-List: archive/latest/1480 X-Loop: zsh-workers@math.gatech.edu Precedence: list Resent-Sender: zsh-workers-request@math.gatech.edu In other shells (bash, ksh93 and pdksh) ulimit affects the shell itself, not only child processes. I think zsh ulimit should behave similarily. Even after ulimit is changed limit can still be used to set limits which affect child processes only. I enable coredumps by defaults in my .zshrc to catch rare zsh bugs but this does not affect login shells so I have no coredumps when zsh crashes (fortunately this does not seem to occur recently). Zoltan