Bug 809924

Summary:	pam floods /var/log/messages when activating atd
Product:	[openSUSE] openSUSE 12.3	Reporter:	Klaus Singvogel <bugzilla>
Component:	Basesystem	Assignee:	Christian Kornacker <ckornacker>
Status:	VERIFIED WONTFIX	QA Contact:	E-mail List <qa-bugs>
Severity:	Normal
Priority:	P5 - None
Version:	Final
Target Milestone:	---
Hardware:	64bit
OS:	SUSE Other
Whiteboard:
Found By:	Community User	Services Priority:
Business Priority:		Blocker:	---
Marketing QA Status:	---	IT Deployment:	---

Description Klaus Singvogel 2013-03-18 09:30:33 UTC

User-Agent:       Mozilla/5.0 (Windows NT 5.1; rv:19.0) Gecko/20100101 Firefox/19.0

The atd is started by cron every 5 minutes.
These default actions (activation and deactivation) are worth a messages in /var/log/messages, even if nothing happens:

Mar 16 23:00:01 host/usr/sbin/cron[14188]: pam_unix(crond:session): session opened for user root by (uid=0)
Mar 16 23:00:01 host /USR/SBIN/CRON[14188]: pam_unix(crond:session): session closed for user root

The reason is pam in file: /etc/pam.d/crond
commenting off line
   session  include        common-session
reduces the verbosity.

Can this be done by default? Maybe there is a more elegant way to solve it...

Reproducible: Always

Steps to Reproduce:
1.
2.
3.



Selected "SUSE Other" as operating system, as "openSUSE-12.3" isn't avail in the list. But this is a "openSUSE-12.3" bugzilla entry.

Comment 1 Michael Calmer 2013-10-02 14:38:55 UTC

I think removing session from crond file is no option.
It might be, that there happens something important.

Removing this message from pam_unix is also not an option. With a real login
it maybe used for audits to find out who logged-in and when.

Thorsten: do you have an idea how we can reduce these messages from cron?

Comment 2 Thorsten Kukuk 2013-10-07 08:44:21 UTC

Removing session from crond by default is no option, correct.

But if somebody does not like the default behavior and does not need the other functionality, he can do it at his own. That's why this are config files and not hardcoded values.

Comment 4 Christian Kornacker 2013-10-22 11:57:33 UTC

Since neither removing session from crond's pam config nor removing the message from pam_unix is an option, I'm closing this as WONTFIX.