From: "David Wolfe" <dwolfe@gforcetech.com>
To: <zsh-workers@sunsite.dk>
Subject: Re: Problems building zsh on QNX 6.1
Date: Tue, 4 Jun 2002 17:00:49 -0400 [thread overview]
Message-ID: <000501c20c0b$7f4fb960$229c9840@SHADOWFAX> (raw)
> ... RLIMIT_RSS and RLIMIT_VMEM are both expanding to '6'.
Hmm. I was curious about this, so I checked <sys/resource.h> on QNX 6.1:
#define RLIMIT_AS 6 /* Limit on address space size. */
#define RLIMIT_VMEM RLIMIT_AS
#define RLIMIT_RSS RLIMIT_AS
RLIMIT_VMEM, RLIMIT_RSS and RLIMIT_AS are all identical. I'm guessing
this is because QNX is a realtime OS and doesn't limit how much memory
one process is allowed to use?
Anyway, I decided to roll up my sleeves and take a crack at fixing this.
It turns out that someone else had already done all the work! I merely
copied a few lines down to where they needed to go.
I humbly submit the following patch. (Please reply directly with
any comments, as I'm not subscribed to the list...)
- Dave
*** rlimits.c Tue Jun 4 16:23:08 2002
--- rlimits.c.new Tue Jun 4 16:27:52 2002
*************** bin_ulimit(char *name, char **argv, char
*** 565,571 ****
# ifdef RLIMIT_MEMLOCK
case RLIMIT_MEMLOCK:
# endif /* RLIMIT_MEMLOCK */
! # ifdef RLIMIT_VMEM
case RLIMIT_VMEM:
# endif /* RLIMIT_VMEM */
# ifdef RLIMIT_AIO_MEM
--- 565,573 ----
# ifdef RLIMIT_MEMLOCK
case RLIMIT_MEMLOCK:
# endif /* RLIMIT_MEMLOCK */
! /* If RLIMIT_VMEM and RLIMIT_RSS are defined and equal, avoid *
! * duplicate case statement. Observed on QNX Neutrino 6.1.0. */
! # if defined(RLIMIT_VMEM) && (!defined(RLIMIT_RSS) || RLIMIT_RSS !=
RLIMIT_VMEM)
case RLIMIT_VMEM:
# endif /* RLIMIT_VMEM */
# ifdef RLIMIT_AIO_MEM
next reply other threads:[~2002-06-04 21:06 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-06-04 21:00 David Wolfe [this message]
2002-06-05 9:07 ` Peter Stephenson
-- strict thread matches above, loose matches on Subject: below --
2002-06-03 1:42 dwolfe
2002-06-03 5:17 ` Borsenkow Andrej
2002-06-03 15:10 ` dwolfe
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='000501c20c0b$7f4fb960$229c9840@SHADOWFAX' \
--to=dwolfe@gforcetech.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).