zsh-workers
 help / color / mirror / code / Atom feed
From: "Bart Schaefer" <schaefer@brasslantern.com>
To: Peter Stephenson <pws@csr.com>,
	zsh-workers@sunsite.dk (Zsh hackers list)
Subject: Re: PATCH: RLIMITS macros
Date: Wed, 2 Apr 2003 03:25:19 +0000	[thread overview]
Message-ID: <1030402032519.ZM6980@candle.brasslantern.com> (raw)
In-Reply-To: <1753.1049221755@csr.com>

On Apr 1,  7:29pm, Peter Stephenson wrote:
}
} What are HAVE_RLIMIT_RSS, HAVE_RLIMIT_VMEM, HAVE_RLIMIT_AS,
} RLIMIT_VMEM_IS_RSS, RLIMIT_VMEM_IS_AS?

After applying the patch from 18425 and rerunning configure, I have:

#define HAVE_RLIMIT_AS 1
#define HAVE_RLIMIT_RSS 1
/* #undef HAVE_RLIMIT_VMEM */
/* #undef RLIMIT_VMEM_IS_RSS */
/* #undef RLIMIT_VMEM_IS_AS */

And after compiling, I now get:

zagzig% ulimit -v 10240
ulimit: bad option: -v

} It's possible to skip the multiplication by 1024 if RLIMIT_AS is defined
} and is not the same as RLIMIT_RSS, but I didn't think that was the case
} here.

That's *exactly* the case here.  The following is all inside enum { }:

/usr/include/bits/resource.h:  RLIMIT_RSS = 5,
/usr/include/bits/resource.h:#define	RLIMIT_RSS RLIMIT_RSS
/usr/include/bits/resource.h:  RLIMIT_AS = 9,
/usr/include/bits/resource.h:#define RLIMIT_AS RLIMIT_AS


  reply	other threads:[~2003-04-02  3:25 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-03-31 10:16 Peter Stephenson
2003-03-31 18:54 ` Bart Schaefer
2003-04-01  9:40   ` Peter Stephenson
2003-04-01 10:20     ` Peter Stephenson
2003-04-01 15:47     ` Bart Schaefer
2003-04-01 16:08       ` Bart Schaefer
2003-04-01 17:04         ` Peter Stephenson
2003-04-01 17:52           ` Bart Schaefer
2003-04-01 18:29             ` Peter Stephenson
2003-04-02  3:25               ` Bart Schaefer [this message]
2003-04-02  9:46                 ` Peter Stephenson
2003-04-03  9:49                   ` Peter Stephenson

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=1030402032519.ZM6980@candle.brasslantern.com \
    --to=schaefer@brasslantern.com \
    --cc=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).