From: Alex Schuster <wonko@wonkology.org>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] Disable fcron logging
Date: Tue, 24 Aug 2010 00:12:09 +0200 [thread overview]
Message-ID: <201008240012.10589.wonko@wonkology.org> (raw)
In-Reply-To: <201008211543.05942.alan.mckinnon@gmail.com>
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
next prev parent reply other threads:[~2010-08-23 22:12 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-08-21 13:25 [gentoo-user] Disable fcron logging Alex Schuster
2010-08-21 13:43 ` Alan McKinnon
2010-08-23 22:12 ` Alex Schuster [this message]
2010-08-24 6:49 ` Alan McKinnon
2010-08-21 19:26 ` Stroller
2010-08-22 10:26 ` Alex Schuster
2010-08-22 19:00 ` Stroller
2010-08-22 19:50 ` Stroller
2010-08-22 21:39 ` Alex Schuster
2010-08-22 22:18 ` Mick
2010-08-24 13:31 ` KDE and hdparm (was: Re: [gentoo-user] Disable fcron logging) Alex Schuster
2010-08-25 9:54 ` [gentoo-user] Re: KDE and hdparm Alex Schuster
2010-08-25 19:14 ` Mick
2010-08-30 16:38 ` KDE and hdparm (was: Re: [gentoo-user] Disable fcron logging) Mick
2010-08-23 18:25 ` [gentoo-user] Disable fcron logging Stroller
2010-08-23 21:30 ` Alex Schuster
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=201008240012.10589.wonko@wonkology.org \
--to=wonko@wonkology.org \
--cc=gentoo-user@lists.gentoo.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox