Zsh Mailing List Archive
Messages sorted by:
Reverse Date,
Date,
Thread,
Author
Re: PATCH: RLIMITS macros
- X-seq: zsh-workers 18428
- From: "Bart Schaefer" <schaefer@xxxxxxxxxxxxxxxx>
- To: Peter Stephenson <pws@xxxxxxx>, zsh-workers@xxxxxxxxxx (Zsh hackers list)
- Subject: Re: PATCH: RLIMITS macros
- Date: Wed, 2 Apr 2003 03:25:19 +0000
- In-reply-to: <1753.1049221755@xxxxxxx>
- Mailing-list: contact zsh-workers-help@xxxxxxxxxx; run by ezmlm
- References: <1753.1049221755@xxxxxxx>
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
Messages sorted by:
Reverse Date,
Date,
Thread,
Author