Bug 176423
Summary: | Looped logging to syslog | ||
---|---|---|---|
Product: | Red Hat Enterprise Linux 4 | Reporter: | Need Real Name <tsp> |
Component: | vixie-cron | Assignee: | Jason Vas Dias <jvdias> |
Status: | CLOSED DUPLICATE | QA Contact: | Brock Organ <borgan> |
Severity: | medium | Docs Contact: | |
Priority: | medium | ||
Version: | 4.0 | CC: | tao |
Target Milestone: | --- | ||
Target Release: | --- | ||
Hardware: | i686 | ||
OS: | Linux | ||
Whiteboard: | |||
Fixed In Version: | Doc Type: | Bug Fix | |
Doc Text: | Story Points: | --- | |
Clone Of: | Environment: | ||
Last Closed: | 2006-01-17 19:40:59 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: |
Description
Need Real Name
2005-12-22 15:59:53 UTC
For each cron job, cron opens a PAM session, to permit audit logging and authentication control with PAM . You can disable the generation of these PAM session messages as indicated in bug 173926 - edit the /etc/pam.d/crond file to read: # # The PAM configuration file for the cron daemon # # auth sufficient pam_rootok.so auth required pam_stack.so service=system-auth auth required pam_env.so account required pam_stack.so service=system-auth account required pam_access.so #session required pam_stack.so service=system-auth session required pam_loginuid.so This will prevent the PAM session log messages being generated for each cron job . Some users may consider the cron PAM session messages useful, and the /etc/pam.d/crond file is user configurable - so disabling the cron PAM session log messages is a user configuration choice, and should not be the default. *** This bug has been marked as a duplicate of 173926 *** |