Alan McKinnon writes:
> Apparently, though unproven, at 15:25 on Saturday 21 August 2010, Alex
> Schuster did opine thusly:
> > There is a nolog option for fcrontab, but I still get this output
> > every minute:
> That will tell fcron not to log stuff.
> It will not tell other apps to not stuff
Right. But I did not know that there are more things involved than cron
itself and the command I am calling. This PAM stuff is new to me, but
maybe I just never noticed it before in my logs. It's no problem when it's
not coming every minute.
> > Aug 21 15:10:06 [fcron] pam_unix(fcron:session): session opened for
> > user root by (uid=0) Aug 21 15:10:08 [fcron]
> > pam_unix(fcron:session): session closed for user root
> >
> > Hmmm... could it be that these entries do not come from fcron itself,
> > but from PAM?
>
> Yes.
>
> Configure your syslogger to devnull these specific entries.
> All three common sysloggers (syslogd,syslog-ng,rsyslog) all come with
> extensive documentation on how to do this.
Hmm, okay. I think there is no perfect solution. When I disable logging of
this PAM stuff, I can only disable it completely, but what if I want to
keep the logging from other jobs that are not run that often? Although for
this case I can use the direct logging of fcron (without nolog), so this
is quite academic. Can anybody still follow me? But thanks for the
clarification.
Meanwhile, I have the script running in /etc/conf.d/local.start, so I have
no syslog output at all and I also can have more updates than only once
per minute.
Wonko
