Bug 86182 - Raising, lowering, and attempting to raise again ulimit for stacksize in bash fails
Raising, lowering, and attempting to raise again ulimit for stacksize in bash...
Product: Red Hat Linux
Classification: Retired
Component: bash (Show other bugs)
i586 Linux
medium Severity medium
: ---
: ---
Assigned To: Tim Waugh
Ben Levenson
Depends On:
  Show dependency treegraph
Reported: 2003-03-16 01:09 EST by Victor J. Orlikowski
Modified: 2007-04-18 12:52 EDT (History)
0 users

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Last Closed: 2003-03-16 06:50:30 EST
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Attachments (Terms of Use)

  None (edit)
Description Victor J. Orlikowski 2003-03-16 01:09:50 EST
From Bugzilla Helper:
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.3) Gecko/20030312

Description of problem:
In the specified bash, on 7.3:
1) ulimit -s 65536
2) ulimit -s 32768
3) ulimit -s 65536

The attempt to re-raise the stacksize fails with the following error:
bash: ulimit: cannot modify stack size limit: Operation not permitted

This does not occur when running bash as root, nor when using tcsh instead of bash.

This can be triggered by lowering the stacksize to *any* value lower than the
initial value set; for example, if step 2 above used 65535, rather than 32768,
the error would still occur.

Version-Release number of selected component (if applicable):

How reproducible:

Steps to Reproduce:
See above description.

Actual Results:  Unable to raise stacksize ulimit again, until new shell started.

Expected Results:  As in tcsh, one should be able to raise and lower the
stacksize ulimit within the range permitted by the soft and hard system limits
(whether architectural, or set by the administrator).

Additional info:
Comment 1 Tim Waugh 2003-03-16 06:50:30 EST
This is exactly as the man page describes.  You are setting the hard limit too,
and you forgot to use the -S option.

Note You need to log in before you can comment on or make changes to this bug.