Bug 132902 - stack settings not correct when ulimit package is installed
Summary: stack settings not correct when ulimit package is installed
Status: RESOLVED FIXED
Alias: None
Product: SUSE LINUX 10.0
Classification: openSUSE
Component: Basesystem (show other bugs)
Version: RC 4
Hardware: Other Other
: P5 - None : Normal
Target Milestone: ---
Assignee: Kurt Garloff
QA Contact: E-mail List
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2005-11-09 12:25 UTC by Dirk Mueller
Modified: 2005-11-28 18:46 UTC (History)
0 users

See Also:
Found By: Other
Services Priority:
Business Priority:
Blocker: ---
Marketing QA Status: ---
IT Deployment: ---


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Dirk Mueller 2005-11-09 12:25:24 UTC
the sysconfig/ulimit text says: 

## Type:        integer(0:99)
## Default:     0
#
# Limit the size of the stack that a single process may allocate.
# Normally, it should be enough to limit virtual and resident size.
# Note that with NPTL, the stack limit determines the stack SIZE
# of multithreaded programs and should thus better not be set.
# Soft limit: Can be increased by non-root up to the hard limit.
# This value corresponds to ulimit -Ss
# Parameter is in percent of physical memory, 0 means no adjustment
# (unlimited).
#
SOFTSTACKLIMIT=0


which reads as if you leave it at the default, you get no stack limit. What actually happens however is that you get the kernel default ulimit, which is arch-dependant (mostly 8MB).
Comment 1 Kurt Garloff 2005-11-14 22:05:17 UTC
Looks like a simple documentation bug to me.
Does changing the last sentence to
# Parameter is in percent of physical memory, 0 means no adjustment
# (the kernel default, arch-dependent, something in the order of 8MB)
#
SOFTSTACKLIMIT=0

I see one little problem: There's no way to set it to unlimited ...
Comment 2 Kurt Garloff 2005-11-28 18:46:57 UTC
Updated package submitted to STABLE.