zsh-workers
 help / color / mirror / code / Atom feed
From: Peter Stephenson <pws@csr.com>
To: zsh-workers@sunsite.dk (Zsh hackers list)
Subject: Re: ulimit strangeness
Date: Fri, 15 Nov 2002 11:55:54 +0000	[thread overview]
Message-ID: <23083.1037361354@csr.com> (raw)
In-Reply-To: ""Bart Schaefer""'s message of "Thu, 14 Nov 2002 16:43:32 GMT." <1021114164332.ZM7641@candle.brasslantern.com>

"Bart Schaefer" wrote:
> zsh% ulimit -v $[200*1024]; limit
> cputime         unlimited
> filesize        unlimited
> datasize        unlimited
> stacksize       8MB
> coredumpsize    unlimited
> memoryuse       unlimited
> maxproc         2040
> descriptors     1024
> memorylocked    unlimited
> addressspace    200kB		<-- Note, not 200 megabytes!
>
> It looks like this has something to do with the convoluted #ifdef that
> prevents duplicate case labels in rlimits.c when both RLIMIT_RSS and
> RLIMIT_VMEM are defined, but I haven't yet figured out what to fix.

My guess is the test `RLIMIT_RSS != RLIMIT_VMEM' is incorrectly failing
in the preprocessor, i.e. it thinks RLIMIT_RSS == RLIMIT_VMEM owing to
the way the definitions are laid out.  Checking
/usr/include/sys/resource.h or carefully hidden equivalent should
confirm or refute this.  The following programme might help.

  #include <stdio.h>
  #include <sys/resource.h>

  int main(int argc, char **argv)
  {
  #if defined(RLIMIT_RSS) && defined(RLIMIT_VMEM)
      printf("You have both definitions.\n");
      if (RLIMIT_RSS == RLIMIT_VMEM)
      {
	  printf("Both have the same value.\n");
      }
      else
      {
	  printf("They have different values.\n");
  #if RLIMIT_RSS == RLIMIT_VMEM
	  printf("!!!You should never see this message!!!\n");
  #endif
      }
  #else
  #ifdef RLIMIT_RSS
      printf("You only have RSS\n");
  #else
  #ifdef RLIMIT_VMEM
      printf("You only have VMEM\n");
  #else
      printf("You have neither definition.\n");
  #endif
  #endif
  #endif

      return 0;
  }

We could probe this more reliably than at present in configure.

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


**********************************************************************
The information transmitted is intended only for the person or
entity to which it is addressed and may contain confidential 
and/or privileged material. 
Any review, retransmission, dissemination or other use of, or
taking of any action in reliance upon, this information by 
persons or entities other than the intended recipient is 
prohibited.  
If you received this in error, please contact the sender and 
delete the material from any computer.
**********************************************************************


       reply	other threads:[~2002-11-15 11:56 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <1021114164332.ZM7641@candle.brasslantern.com>
2002-11-15 11:55 ` Peter Stephenson [this message]
2002-11-15 12:57   ` jarausch
2002-11-16  3:13   ` Bart Schaefer
2002-11-18 10:31     ` 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=23083.1037361354@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).