[7946] in testers

home help back first fref pref prev next nref lref last post

Re: syslog spew

daemon@ATHENA.MIT.EDU (Tim Abbott)
Sat Mar 14 14:04:32 2009

Date: Sat, 14 Mar 2009 14:03:10 -0400 (EDT)
From: Tim Abbott <tabbott@MIT.EDU>
To: Camilla R Fox <cfox@mit.edu>
cc: testers@mit.edu
In-Reply-To: <alpine.DEB.1.10.0903131640360.31244@vinegar-pot.mit.edu>
Message-ID: <alpine.DEB.1.10.0903131648520.31244@vinegar-pot.mit.edu>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII

On Fri, 13 Mar 2009, Tim Abbott wrote:

> On Fri, 13 Mar 2009, Camilla R Fox wrote:
> 
> > 
> > The *:16 cron jobs seem to generate rather noisy log messages every
> > single time:
> > 
> > Mar 13 07:16:47 M66-080-4.MIT.EDU CRON[12639]: pam_krb524: No krb5 cache found
> > Mar 13 07:16:47 M66-080-4.MIT.EDU CRON[12639]: pam_athena_locker: No Kerberos ticket cache; not attaching locker
> > Mar 13 07:16:47 M66-080-4.MIT.EDU CRON[12639]: pam_mktemp: No variable to set
> > Mar 13 07:16:47 M66-080-4.MIT.EDU CRON[12639]: pam_krb524: No krb5 cache found
> > Mar 13 07:16:47 M66-080-4.MIT.EDU CRON[12639]: pam_mktemp: Nothing to cleanup
> 
> I'll plan to investigate these sometime this weekend.

Thanks for mentioning this syslog spam!  I consider all three of these 
issues to be bugs.

I've changed pam_athena_locker and pam_krb524 to only log about missing 
Kerberos ticket caches when they're configured in debugging mode.

The pam_mktemp messages are actually the result of a bug in our PAM 
configuration; I've committed a fix to it as well.  

All of these changes are now uploaded to the -proposed repositories.  I 
expect them to be released to the clusters in a few days.

	-Tim Abbott

home help back first fref pref prev next nref lref last post