----- Original Message ----- From: "Jess Anderson" <anderson@xxxxxxxx>
To: "Fedora Core Mailing List" <fedora-list@xxxxxxxxxx>
Sent: Friday, 25 February, 2005 18:56
Subject: How to stop crond logging to syslog?
Every time cron wakes up, it logs authentication (PAM) actions to syslog. Not especially useful for a one-user (plus root) system, these messages mostly fill up space:
Feb 25 11:21:01 seth crond(pam_unix)[4381]: session opened for user anderson by (uid=0)
Feb 25 11:21:02 seth crond(pam_unix)[4381]: session closed for user anderson
Feb 25 11:25:01 seth crond(pam_unix)[4396]: session opened for user root by (uid=0)
Feb 25 11:25:01 seth crond(pam_unix)[4396]: session closed for user root
Feb 25 11:27:01 seth crond(pam_unix)[4454]: session opened for user anderson by (uid=0)
Feb 25 11:27:02 seth crond(pam_unix)[4454]: session closed for user anderson
Feb 25 11:30:01 seth crond(pam_unix)[4497]: session opened for user root by (uid=0)
Feb 25 11:30:01 seth crond(pam_unix)[4500]: session opened for user root by (uid=0)
Feb 25 11:30:01 seth crond(pam_unix)[4497]: session closed for user root
Feb 25 11:30:01 seth crond(pam_unix)[4500]: session closed for user root
As far as I can see this logging is compiled in, rather than being controlled by /etc/syslog.conf. Of maybe (entirely possible) I'm confused. The man pages don't mention options or other alternatives, apparently.
Suggestions welcome.
I have found a 'solution'
I disabled the session line in /etc/pam.d/crond
this line : session required /lib/security/$ISA/pam_stack.so service=system-auth
to this line : #session required /lib/security/$ISA/pam_stack.so service=system-auth
now i dont have any crond(pam_unix) messages anymore in my messages file, but i dont know if might be missing something important now, guess not because in the past I never saw them either :)
Edwin