|Summary:||vixie-cron missing pam configuration for limits|
|Product:||Red Hat Enterprise Linux 3||Reporter:||Bastien Nocera <bnocera>|
|Component:||vixie-cron||Assignee:||Jason Vas Dias <jvdias>|
|Status:||CLOSED WONTFIX||QA Contact:||Brock Organ <borgan>|
|Fixed In Version:||vixie-cron-4.1-6_EL3||Doc Type:||Bug Fix|
|Doc Text:||Story Points:||---|
|Last Closed:||2006-02-21 19:08:20 UTC||Type:||---|
|oVirt Team:||---||RHEL 7.3 requirements from Atomic Host:|
Description Bastien Nocera 2005-05-10 09:10:15 UTC
+++ This bug was initially created as a clone of Bug #157290 +++ In the /etc/security/limits.conf file I increase, for example, the number of open file handles allowed for a process. # grep nofile /etc/security/limits.conf dan soft nofile 10000 dan hard nofile 20000 In an SSH session I can verify the limits are being applied: $ ulimit -n 10000 If, however, I setup a cron job as this user: $ crontab -l * * * * * /bin/bash -c "ulimit > /tmp/ulimits.txt" If I then look at the output the limits are not being applied $ grep "open files" /tmp/ulimits.txt open files (-n) 1024 A little poking around reveals that the vixie-cron RPM is missing the PAM config file neccessary to have session limits applied. If I create a file # cat > /etc/pam.d/cron <<EOF #%PAM-1.0 auth required pam_stack.so service=system-auth account required pam_stack.so service=system-auth password required pam_stack.so service=system-auth session required pam_stack.so service=system-auth EOF Restart the cron daemon # /etc/init.d/crond restart Then, wait for the job to run again it now picks up limits correctly $ grep "open files" /tmp/ulimits.txt open files (-n) 10000 The lack of this PAM config is causing application jobs that would otherwise work, to fail
Comment 1 Jason Vas Dias 2005-05-10 12:09:23 UTC
In RHEL-3, vixie-cron has no PAM support. PAM support will be added with vixie-cron-4.1-6_EL3, which will hopefully be in RHEL-3-U6, and which would fix this problem.
Comment 2 Jason Vas Dias 2005-05-10 12:19:32 UTC
*** This bug has been marked as a duplicate of 157290 ***
Comment 4 Red Hat Bugzilla 2006-02-21 19:08:20 UTC
Changed to 'CLOSED' state since 'RESOLVED' has been deprecated.