Bug 176423 - Looped logging to syslog
Summary: Looped logging to syslog
Status: CLOSED DUPLICATE of bug 173926
Alias: None
Product: Red Hat Enterprise Linux 4
Classification: Red Hat
Component: vixie-cron
Version: 4.0
Hardware: i686
OS: Linux
Target Milestone: ---
: ---
Assignee: Jason Vas Dias
QA Contact: Brock Organ
Depends On:
TreeView+ depends on / blocked
Reported: 2005-12-22 15:59 UTC by Need Real Name
Modified: 2018-10-19 20:50 UTC (History)
1 user (show)

Clone Of:
Last Closed: 2006-01-17 19:40:59 UTC

Attachments (Terms of Use)

Description Need Real Name 2005-12-22 15:59:53 UTC
From Bugzilla Helper:
User-Agent: Mozilla/4.0 (compatible; MSIE 6.0; Windows NT 5.1; SV1)

Description of problem:
Every five minutes cron wakes up, it logs authentication (PAM) actions to syslog. The root in this time not login to the system.
This message repeat every 5 minutes (with different PID):

Feb 20 11:30:01 seta crond(pam_unix)[4497]: session opened for user root by (uid=0)
Feb 20 11:30:01 seta crond(pam_unix)[4500]: session opened for user root by (uid=0)
Feb 20 11:30:01 seta crond(pam_unix)[4497]: session closed for user root
Feb 20 11:30:01 seta crond(pam_unix)[4500]: session closed for user root

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

How reproducible:

Steps to Reproduce:
1.install RHEL 4.0 update 2
2.login to the system
3.tail -f /var/log/secure

Additional info:

it looks like

Comment 1 Jason Vas Dias 2006-01-17 19:40:59 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 ***

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