Bug 157290
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 DUPLICATE | QA Contact: | Brock Organ <borgan> |
Severity: | medium | Docs Contact: | |
Priority: | medium | ||
Version: | 3.0 | CC: | benl, nalin, tmraz |
Target Milestone: | --- | ||
Target Release: | --- | ||
Hardware: | All | ||
OS: | Linux | ||
Whiteboard: | |||
Fixed In Version: | vixie-cron-4.1-6_EL3 | Doc Type: | Bug Fix |
Doc Text: | Story Points: | --- | |
Clone Of: | Environment: | ||
Last Closed: | 2006-02-21 19:08:20 UTC | Type: | --- |
Regression: | --- | Mount Type: | --- |
Documentation: | --- | CRM: | |
Verified Versions: | Category: | --- | |
oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
Cloudforms Team: | --- | Target Upstream Version: | |
Embargoed: | |||
Bug Depends On: | |||
Bug Blocks: | 170445 |
Description
Bastien Nocera
2005-05-10 09:08:40 UTC
Nope, this doesn't fix the problem at all. It only appears so to you. The RHEL-3 vixie-cron version 3.0.1 doesn't have a pam support at all. The reason why your trick works is that the limits established in the bash session where you issue /etc/init.d/crond restart apply to the crond daemon and thus apply to the user's processes called according to the crontab. The RHEL-4 vixie-cron has pam support implemented. vixie-cron currently does not support PAM in RHEL-3 . You can download vixie-cron-4.1-6_EL3, which does support PAM, and which will hopefully be in RHEL-3-U6, from: http://people.redhat.com/~jvdias/vixie-cron/RHEL-3/ *** Bug 157291 has been marked as a duplicate of this bug. *** *** This bug has been marked as a duplicate of 5162 *** BTW, the PAM configuration file for vixie-cron-4.1+ is /etc/pam.d/crond , not /etc/pam.d/cron This bug is fixed with vixie-cron-4.1-8_EL3, available from: http://people.redhat.com/~jvdias/cron/RHEL-3 and should be considered for inclusion in RHEL-3-U7 . Changed to 'CLOSED' state since 'RESOLVED' has been deprecated. |