From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 14324 invoked from network); 14 Jun 2004 13:08:54 -0000 Received: from thor.dotsrc.org (HELO a.mx.sunsite.dk) (130.225.247.86) by ns1.primenet.com.au with SMTP; 14 Jun 2004 13:08:54 -0000 Received: (qmail 6880 invoked from network); 14 Jun 2004 13:08:45 -0000 Received: from sunsite.dk (130.225.247.90) by a.mx.sunsite.dk with SMTP; 14 Jun 2004 13:08:45 -0000 Received: (qmail 19483 invoked by alias); 14 Jun 2004 13:08:36 -0000 Mailing-List: contact zsh-workers-help@sunsite.dk; run by ezmlm Precedence: bulk X-No-Archive: yes X-Seq: 20039 Received: (qmail 19474 invoked from network); 14 Jun 2004 13:08:36 -0000 Received: from thor.dotsrc.org (HELO a.mx.sunsite.dk) (qmailr@130.225.247.86) by sunsite.dk with SMTP; 14 Jun 2004 13:08:33 -0000 Received: (qmail 6572 invoked from network); 14 Jun 2004 13:08:33 -0000 Received: from lhuumrelay3.lnd.ops.eu.uu.net (62.189.58.19) by a.mx.sunsite.dk with SMTP; 14 Jun 2004 13:08:31 -0000 Received: from MAILSWEEPER01.csr.com (mailhost1.csr.com [62.189.183.235]) by lhuumrelay3.lnd.ops.eu.uu.net (8.11.0/8.11.0) with ESMTP id i5ED84v13610 for ; Mon, 14 Jun 2004 13:08:05 GMT Received: from EXCHANGE02.csr.com (unverified [192.168.137.45]) by MAILSWEEPER01.csr.com (Content Technologies SMTPRS 4.3.12) with ESMTP id for ; Mon, 14 Jun 2004 14:07:25 +0100 Received: from news01.csr.com ([192.168.143.38]) by EXCHANGE02.csr.com with Microsoft SMTPSVC(5.0.2195.6713); Mon, 14 Jun 2004 14:11:08 +0100 Received: from news01.csr.com (localhost.localdomain [127.0.0.1]) by news01.csr.com (8.12.11/8.12.11) with ESMTP id i5ED820e015227 for ; Mon, 14 Jun 2004 14:08:02 +0100 Received: from csr.com (pws@localhost) by news01.csr.com (8.12.11/8.12.11/Submit) with ESMTP id i5ED81Kl015224 for ; Mon, 14 Jun 2004 14:08:02 +0100 Message-Id: <200406141308.i5ED81Kl015224@news01.csr.com> X-Authentication-Warning: news01.csr.com: pws owned process doing -bs To: Zsh workers Subject: Re: setting resource limits In-reply-to: "Oliver Kiddle"'s message of "Mon, 14 Jun 2004 13:31:47 +0200." <4754.1087212707@trentino.logica.co.uk> Date: Mon, 14 Jun 2004 14:08:01 +0100 From: Peter Stephenson X-OriginalArrivalTime: 14 Jun 2004 13:11:08.0398 (UTC) FILETIME=[0E7978E0:01C45211] X-Spam-Checker-Version: SpamAssassin 2.63 on a.mx.sunsite.dk X-Spam-Level: X-Spam-Status: No, hits=0.0 required=6.0 tests=BAYES_50 autolearn=no version=2.63 X-Spam-Hits: 0.0 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 ' 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 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 **********************************************************************