zsh-workers
 help / color / mirror / code / Atom feed
From: schaefer@z-code.ncd.com (Barton E. Schaefer)
To: Zoltan Hidvegi <hzoli@cs.elte.hu>,
	zsh-workers@math.gatech.edu (Zsh hacking and development)
Subject: Re: ulimit should limit the shell?
Date: Sun, 30 Jun 1996 00:30:21 -0700	[thread overview]
Message-ID: <960630003021.ZM11861@zyrcon.z-code.com> (raw)
In-Reply-To: Zoltan Hidvegi <hzoli@cs.elte.hu> "ulimit should limit the shell?" (Jun 29,  5:53pm)

On Jun 29,  5:53pm, Zoltan Hidvegi wrote:
} Subject: ulimit should limit the shell?
}
} 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.

According to zshbuiltins.1, `ulimit' affects child processes only, but
`limit' affects both zsh and its children.  Is this description wrong?

I believe the reason for the zsh behavior is that the zsh `limit' is
derived from csh/tcsh, where `ulimit' does not exist.  Why `ulimit' is
not simply a synonym for `limit' I do not know; `ulimit' got put in to
zsh during one of the stretches when I wasn't paying much attention to
the mailing list.

} 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).

If all you're worried about is having the ability to affect the shell
itself, use `limit' instead of `ulimit'.  If you're worried about the
ksh compatibility issue, I don't know of any shell other than zsh that
allows you to set limits for children differently from the limits of
the parent shell; so for all I care, the difference between `ulimit'
and `limit' can go away, or be made available only throug a switch
given to `ulimit'.

-- 
Bart Schaefer
schaefer@z-code.com
http://www.well.com/www/barts



  reply	other threads:[~1996-06-30  7:41 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
1996-06-29 15:53 Zoltan Hidvegi
1996-06-30  7:30 ` Barton E. Schaefer [this message]
1996-06-30  9:26   ` Geoff Wing

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=960630003021.ZM11861@zyrcon.z-code.com \
    --to=schaefer@z-code.ncd.com \
    --cc=hzoli@cs.elte.hu \
    --cc=zsh-workers@math.gatech.edu \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
Code repositories for project(s) associated with this public inbox

	https://git.vuxu.org/mirror/zsh/

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).