Bug 168790 - pam_limits sets wrong values for corefile, etc (missed break)
pam_limits sets wrong values for corefile, etc (missed break)
Status: CLOSED RAWHIDE
Product: Fedora
Classification: Fedora
Component: pam (Show other bugs)
rawhide
All Linux
medium Severity medium
: ---
: ---
Assigned To: Tomas Mraz
: Regression
Depends On:
Blocks:
  Show dependency treegraph
 
Reported: 2005-09-20 06:35 EDT by Anton Guda
Modified: 2007-11-30 17:11 EST (History)
0 users

See Also:
Fixed In Version: pam-0.80-8
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Environment:
Last Closed: 2005-09-20 17:55:36 EDT
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---


Attachments (Terms of Use)
patch to fix pam_limits bug (531 bytes, patch)
2005-09-20 06:36 EDT, Anton Guda
no flags Details | Diff

  None (edit)
Description Anton Guda 2005-09-20 06:35:21 EDT
From Bugzilla Helper:
User-Agent: Mozilla/5.0 (compatible; Konqueror/3.4; Linux; X11; ru) KHTML/3.4.2 (like Gecko)

Description of problem:
When pam_limits used in system-auth, and in /etc/security/limits.conf 
defined values for corefile size, max locaked memory, 
wrong values (really 19) is passwd to setrlimits. 
As a resilt, no core file may be created, 
no soft limit may be changed. 

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

How reproducible:
Always

Steps to Reproduce:
1. include pam_limits in system-auth (session) 
2. set some good values for limits 
3. login and ulimit -Hc  
   

Actual Results:  Zero (0) is returned  
( 19/1024 = 0 ) 
 

Expected Results:  The same value, as in limits.conf must be returned (and setted) 

Additional info:

its a missed bread bug -- patch provided
Comment 1 Anton Guda 2005-09-20 06:36:29 EDT
Created attachment 119019 [details]
patch to fix pam_limits bug
Comment 2 Tomas Mraz 2005-09-20 08:12:24 EDT
Thank you for spotting this.
I'll also apply it upstream.

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