u...@debian.org (Aaron M. Ucko) writes: > Russ Allbery <r...@debian.org> writes:
>> 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.... > Good question; it looks like my (mostly default) sudo configuration > leaks KRB5CCNAME, so a recent run of sudo aptitude safe-upgrade that > resulted in restarting cron caused it to pick up my personal setting > thereof. :-/ I'll adjust my setup to avoid that, but still feel it's > enough of a gotcha that more widespread changes might be in order. I agree with you, but I don't think it's pam-afs-session where the bug is. This is a bug that's been bothering me for a long time. I'm not sure if aptitude or dpkg should be cleaning out the environment before invoking maintainer scripts, maintainer scripts should be cleaning the environment before running invoke-rc.d, or invoke-rc.d should be cleaning the environment, but *something* in that path really should. In the past, I've seen debconf environment variables leaked into xinetd and then passed along to subsequent user logins, which then breaks subsequent aptitude runs. -- Russ Allbery (r...@debian.org) <http://www.eyrie.org/~eagle/> -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
