zsh-workers
 help / color / mirror / code / Atom feed
From: Bart Schaefer <schaefer@brasslantern.com>
To: zsh-workers@sunsite.dk
Subject: "limit" broken on 64bit Linux?
Date: Mon, 26 Jun 2006 16:29:31 -0700 (PDT)	[thread overview]
Message-ID: <Pine.LNX.4.64.0606261620310.28114@toltec.zanshin.com> (raw)

We just installed a spanking-new Opteron machine with CentOS 4.3 for
the x86_64 architecture on it.  This is equivalent to RedHat EL4u3 and
comes with zsh-4.2.0 as a precompiled RPM.

The first thing I did was install my cvs-controlled zsh environment and
log out and back in.  I get:

/home/schaefer/.zsh/.zlogin:unlimit:29: no such resource: cputime

The "ulimit" (as opposed to uNlimit) command works fine, but the "limit"
command has nothing.

schaefer[4] zmodload zsh/rlimits
zmodload: module zsh/rlimits already loaded.
schaefer[5] limit
schaefer[6] ulimit
unlimited
schaefer[7] ulimit -a
cpu time (seconds)         unlimited
file size (blocks)         unlimited
data seg size (kbytes)     unlimited
stack size (kbytes)        10240
core file size (blocks)    0
resident set size (kbytes) unlimited
processes                  28663
file descriptors           1024
locked-in-memory size (kb) 32
address space (kb)         unlimited
file locks                 unlimited
1024
819200
schaefer[8] uname -a
Linux mercury.zanshin.com 2.6.9-34.0.1.EL #1 Wed May 24 05:05:44 CDT 2006 x86_64 x86_64 x86_64 GNU/Linux


It'll be a while before I get a chance to attempt recompiling zsh on this
machine.  Has anyone else seen this problem?  How can it even occur?


             reply	other threads:[~2006-06-26 23:29 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-06-26 23:29 Bart Schaefer [this message]
2006-06-27 11:42 ` Peter Stephenson
2006-06-27 15:29   ` Bart Schaefer
2006-07-01 20:04   ` Bart Schaefer
2006-07-02 21:50   ` Bart Schaefer
2006-07-02 23:41     ` Bart Schaefer
2006-07-03  9:20       ` 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=Pine.LNX.4.64.0606261620310.28114@toltec.zanshin.com \
    --to=schaefer@brasslantern.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).