Red Hat Bugzilla – Bug 171546
limits.conf don't pick "unlimited" settings
Last modified: 2007-11-30 17:11:15 EST
From Bugzilla Helper:
User-Agent: Mozilla/5.0 (X11; U; Linux x86_64; en-US; rv:1.7.12) Gecko/20050922 Fedora/1.0.7-1.1.fc4 Firefox/1.0.7
Description of problem:
I want to set the memlock ulimit parameter to "unlimited" - this is to be able to run the crossover office plugin. According to the codeweaver people the ulimit -l setting must be "unlimited" for the plugin to wrok.
If I raise the value in limts.conf, I can indeed increase the ulimit -l argument. However, if i set the hard limit for memlock in limits.conf to "unlimited" I cant increase the value of the memlock limit to more than 32, the default value.
Version-Release number of selected component (if applicable):
Steps to Reproduce:
1.Set memlock lhard imit in /etc/security/limits.conf ton 'unlimited'
2.log out, and in again as regular user.
3. $ ulimit -l 200
4. Watch output from ulimit, memlock is stoll 32. Should be 200.
Actual Results: memlock limit is default value, 32
Expected Results: memlock limit = 200,
This seems to be be recently fixed in RH server, see https://rhn.redhat.com/errata/RHBA-2005-526.html
Created attachment 120292 [details]
patch based on RHS patch for pam-0.77
This patch Works For Me (tm). It's one of the patches for 0.77 handling
decoding of the limits.conf as described in the Errata adopted for 0.79.