zsh-workers
 help / color / mirror / code / Atom feed
From: Geoff Wing <mason@werple.net.au>
To: zsh-workers@math.gatech.edu (zsh-list)
Subject: Re: ulimit should limit the shell?
Date: Sun, 30 Jun 1996 19:26:32 +1000 (EST)	[thread overview]
Message-ID: <199606300926.JAA26906@werple.net.au> (raw)
In-Reply-To: <960630003021.ZM11861@zyrcon.z-code.com> from "Barton E. Schaefer" at Jun 30, 96 00:30:21 am

:} 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?

It's not really a clear description in the manual.

Running limit/ulimit/unlimit sets limits on all child processes.
Running "limit -s" sets the limits for the shell (using the same limits
the child processes are currently set to).
So to have different limits for child and shell you need to setup the
shell's limits first, limit -s, then set the child's limits.

: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 don't know where ulimit came from, though bash has it.  However it's
not fully compatible with the bash ulimit.  If it's been put in to
provide some sort of compatibility with bash (or anything else) it
probably should be changed to be more compatible.


-- 
Mason [G.C.W]  mason@werple.mira.net.au    "Hurt...Agony...Pain...LOVE-IT"



      reply	other threads:[~1996-06-30  9:46 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
1996-06-30  9:26   ` Geoff Wing [this message]

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=199606300926.JAA26906@werple.net.au \
    --to=mason@werple.net.au \
    --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).