From: Micah Cowan <micah@cowan.name>
To: zsh-workers@sunsite.dk
Subject: Re: Bug in ulimit ?
Date: Tue, 17 Apr 2007 03:55:27 -0700 [thread overview]
Message-ID: <4624A79F.1020107@cowan.name> (raw)
In-Reply-To: <20070417104303.GB4955@sc.homeunix.net>
Stephane Chazelas wrote:
> On Tue, Apr 17, 2007 at 03:04:55AM -0700, Micah Cowan wrote:
> [...]
>> % ulimit -t 0
>> % ( ulimit -t; while :; do :; done )
>> 0
>> << watch the CPU time used climb in top >>
>> ^C
> [...]
>> It therefore appears that while the manpage is correct for hard limits,
>> soft limits of 0 are still treated as unlimited.
> [...]
>
> ulimit -t
>
> doesn't set the limit to 0 but to infinity (in effect, to the
> hard limit).
>
> It's ulimit -t 0
> to set the limit to 0 (well actually, 1 second in that case).
>
Originally responded to this directly, but then realized that the
veracity of this statement is pertinent to the next message I sent as
well, so it's worth addressing on-list, in case it isn't clear to others.
ulimit -t
doesn't set the limit _at_all_; it prints it (hence the "0", above).
--
Micah J. Cowan
Programmer, musician, typesetting enthusiast, gamer...
http://micah.cowan.name/
next prev parent reply other threads:[~2007-04-17 10:55 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-04-17 9:00 David Peer
2007-04-17 9:30 ` Micah Cowan
2007-04-17 9:33 ` David Peer
2007-04-17 9:42 ` Stephane Chazelas
2007-04-17 10:04 ` Micah Cowan
2007-04-17 10:43 ` Stephane Chazelas
2007-04-17 10:55 ` Micah Cowan [this message]
2007-04-17 12:53 ` Stephane Chazelas
2007-04-17 13:03 ` Stephane Chazelas
2007-04-17 13:24 ` Stephane Chazelas
2007-04-17 13:34 ` Stephane Chazelas
2007-04-17 13:54 ` David Peer
2007-04-17 13:57 ` David Peer
2007-04-17 15:02 ` [OT] " Stephane Chazelas
2007-04-17 10:49 ` Micah Cowan
2007-04-17 14:15 ` Tom Alsberg
2007-04-17 15:48 ` David Peer
[not found] ` <20070417151501.GH4955@sc.homeunix.net>
2007-04-18 7:46 ` (Off-Topic) " Tom Alsberg
2007-04-18 8:22 ` Stephane Chazelas
2007-04-18 9:23 ` (Off-Topic) Bug in ulimit? Tom Alsberg
2007-04-18 10:10 ` Stephane Chazelas
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=4624A79F.1020107@cowan.name \
--to=micah@cowan.name \
--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).