Bug 170809 - vixie cron is not pam aware
vixie cron is not pam aware
Product: Red Hat Enterprise Linux 3
Classification: Red Hat
Component: vixie-cron (Show other bugs)
All Linux
medium Severity medium
: ---
: ---
Assigned To: Jason Vas Dias
Brock Organ
: FutureFeature
Depends On: 5162
Blocks: 161600
  Show dependency treegraph
Reported: 2005-10-14 12:19 EDT by Jason Vas Dias
Modified: 2007-11-30 17:07 EST (History)
2 users (show)

See Also:
Fixed In Version: RHSA-2005:0117
Doc Type: Enhancement
Doc Text:
Story Points: ---
Clone Of:
Last Closed: 2006-05-01 14:00:02 EDT
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 Jason Vas Dias 2005-10-14 12:19:52 EDT
+++ This bug was initially created as a clone of Bug #5162 +++

vixie cron does not use pam and also does not read
/etc/security/limits.conf file. The problem is that if
i normally set limits for all users (number of processes, amount of memory, etc)
with just editing /etc/pam.d/(ssh,login,you name it) file
and setting it to use /etc/security/pam_limits.so, then i cant do this for cron.
And users can execute programs by setting cronjobs or at jobs.
To those programs the limits do not apply and so can user override limits set by

-- Additional comment from notting@redhat.com on 1999-09-17 10:44 EST --
*** This bug has been marked as a duplicate of 5160 ***

-- Additional comment from jvdias@redhat.com on 2005-05-10 08:22 EST --
*** Bug 157290 has been marked as a duplicate of this bug. ***

-- Additional comment from dff@redhat.com on 2005-07-20 17:58 EST --
Withholding PM ACK; vixie-cron does not currently have a QA slot allocated to it
for U6:
Comment 1 Jason Vas Dias 2005-10-14 12:20:52 EDT
This bug is fixed with vixie-cron-4.1-8_EL3, available from:
and should be considered for inclusion in RHEL-3-U7 .
Comment 3 Jason Vas Dias 2006-05-01 14:00:02 EDT
Fixed with vixie-cron-4.1-10.EL3, currently in RHEL-3-U7 with errata

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