/etc/pam.d/common-session-noninteractive:
---
session [success=1 default=ignore] pam_succeed_if.so service in cron quiet
use_uid
Hello,
It would be nice to have the solution proposed by Javier
Fernandez-Sanguino Peña on #36.
If the cron is running frequently, it can generate a lot of messages. As
example, on systems with limited resources, those messages can be can be
worthless.
In the case that the current
FWIW, this bug is the same as one reported in Red Hat in
https://bugzilla.redhat.com/show_bug.cgi?id=165571 (they 'fixed' this
through PAM, see below)
Since the 3.0pl1-107 package release of cron cron uses
'common-session-noninteractive' in its PAM configuration instead of
'common-session'.
I
On Sat, Aug 07, 2010 at 02:32:27AM +0200, Javier Fern?ndez-Sanguino Pe?a wrote:
In Debian, to do this add the following line before the pam_unix.so call
in /etc/pam.d/common-session-noninteractive:
I don't think the change requested in this bug report should be made
(actually, it's at odds with bug #543303 that I've just filed). I believe
that in the general case, we do want pam_unix logging here, just as we do
for any other sort of session; and there are other sorts of session modules
that
Package: cron
Version: 3.0pl1-86
Severity: wishlist
My disk doesn't stay spun-down very long, even with laptop-mode. I
discovered the problem was syslog doing syncs to auth.log whenever a
cron job runs. (I have a package, lockout, that runs a cron job every
minute.) cron logs to auth.log
6 matches
Mail list logo
