"Aaron M. Ucko" <[email protected]> writes: > Since upgrading libpam-afs-session from version 2.2-1 to version > 2.4-1, I've found that cron's invocations thereof (thanks to its > presence in /etc/pam.d/common-session-noninteractive) result in syslog > messages of the form
> Jun 19 17:15:01 tux64 CRON[2471]: pam_afs_session(cron:session): aklog > program /usr/bin/aklog returned 4 > which logcheck conservatively considers noteworthy. Could you please > adjust it to do nothing, or at least not whine if aklog fails, if > there's no sign that it has any actual tickets to work with? Why is your crond running with KRB5CCNAME set in its environment? I suspect that at some point you restarted crond with a dirty environment, probably from a user login.... -- Russ Allbery ([email protected]) <http://www.eyrie.org/~eagle/> -- To UNSUBSCRIBE, email to [email protected] with a subject of "unsubscribe". Trouble? Contact [email protected]
