From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from pigeon.gentoo.org ([208.92.234.80] helo=lists.gentoo.org) by finch.gentoo.org with esmtp (Exim 4.60) (envelope-from ) id 1OnfG9-0006CN-MV for garchives@archives.gentoo.org; Mon, 23 Aug 2010 22:12:55 +0000 Received: from pigeon.gentoo.org (localhost [127.0.0.1]) by pigeon.gentoo.org (Postfix) with SMTP id 7F2EDE0995; Mon, 23 Aug 2010 22:12:12 +0000 (UTC) Received: from mx.virtyou.com (mx.virtyou.com [94.23.166.77]) by pigeon.gentoo.org (Postfix) with ESMTP id 437E1E0990 for ; Mon, 23 Aug 2010 22:12:12 +0000 (UTC) Received: from weird.localnet (p4FF04EE7.dip.t-dialin.net [79.240.78.231]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by mx.virtyou.com (Postfix) with ESMTPSA id 5AE254A8290 for ; Tue, 24 Aug 2010 00:12:12 +0200 (CEST) From: Alex Schuster To: gentoo-user@lists.gentoo.org Subject: Re: [gentoo-user] Disable fcron logging Date: Tue, 24 Aug 2010 00:12:09 +0200 User-Agent: KMail/1.13.5 (Linux/2.6.35-tuxonice; KDE/4.5.0; x86_64; ; ) References: <201008211525.35115.wonko@wonkology.org> <201008211543.05942.alan.mckinnon@gmail.com> In-Reply-To: <201008211543.05942.alan.mckinnon@gmail.com> Precedence: bulk List-Post: List-Help: List-Unsubscribe: List-Subscribe: List-Id: Gentoo Linux mail X-BeenThere: gentoo-user@lists.gentoo.org Reply-to: gentoo-user@lists.gentoo.org MIME-Version: 1.0 Content-Type: Text/Plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit Message-Id: <201008240012.10589.wonko@wonkology.org> X-Archives-Salt: 696612d9-4d32-4669-bede-eb8570d4f639 X-Archives-Hash: e89dac8e813034ef03794e7595e202a3 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