zsh-workers
 help / color / mirror / code / Atom feed
From: Peter Stephenson <pws@csr.com>
To: Zsh workers <zsh-workers@sunsite.dk>
Subject: Re: setting resource limits
Date: Mon, 14 Jun 2004 14:08:01 +0100	[thread overview]
Message-ID: <200406141308.i5ED81Kl015224@news01.csr.com> (raw)
In-Reply-To: "Oliver Kiddle"'s message of "Mon, 14 Jun 2004 13:31:47 +0200." <4754.1087212707@trentino.logica.co.uk>

Oliver Kiddle wrote:
> Basically, the suggestion is that it should be possible to set resource
> limits numerically with e.g. `ulimit 4 1024'. I can see how this could
> be worth a lot to anyone implementing a new resource limit. Is that
> difficult to implement? Would it be vaguely portable?

It's easy if you impose limitations: e.g. `ulimit <number>' is treated
as setting RLIMIT_FSIZE, so you couldn't query limits like that (without an
extra option).  For example, the following (undocumented).

By the way, `ulimit -a' doesn't list the options applying to each limit
as it does in bash, so you're left guessing how to set the limit you
want.

Index: Src/Builtins/rlimits.c
===================================================================
RCS file: /cvsroot/zsh/zsh/Src/Builtins/rlimits.c,v
retrieving revision 1.11
diff -u -r1.11 rlimits.c
--- Src/Builtins/rlimits.c	2 Jun 2004 22:14:47 -0000	1.11
+++ Src/Builtins/rlimits.c	14 Jun 2004 13:07:16 -0000
@@ -555,7 +555,9 @@
 		}
 	    }
 	}
-	if (!*argv || **argv == '-') {
+	if (res < 0 && *argv && idigit(**argv) && argv[1])
+	    res = (int)zstrtol(*argv++, NULL, 10);
+	else if (!*argv || **argv == '-') {
 	    if (res < 0) {
 		if (*argv || nres)
 		    continue;


-- 
Peter Stephenson <pws@csr.com>                  Software Engineer
CSR Ltd., Science Park, Milton Road,
Cambridge, CB4 0WH, UK                          Tel: +44 (0)1223 692070


**********************************************************************
This email and any files transmitted with it are confidential and
intended solely for the use of the individual or entity to whom they
are addressed. If you have received this email in error please notify
the system manager.

This footnote also confirms that this email message has been swept by
MIMEsweeper for the presence of computer viruses.

www.mimesweeper.com
**********************************************************************


  reply	other threads:[~2004-06-14 13:08 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-06-14 11:31 Oliver Kiddle
2004-06-14 13:08 ` Peter Stephenson [this message]
2004-06-14 15:21   ` Peter Stephenson
2004-06-14 15:42     ` Wayne Davison
2004-06-14 15:46       ` Peter Stephenson
2004-06-14 15:59     ` Oliver Kiddle
2004-06-14 16:54       ` Peter Stephenson
2004-06-30 10:12         ` PATCH: setting unknown resource limits, again Peter Stephenson
2004-06-14 19:14 ` setting resource limits Dan Nelson

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=200406141308.i5ED81Kl015224@news01.csr.com \
    --to=pws@csr.com \
    --cc=zsh-workers@sunsite.dk \
    /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).