Hi, Russ! Thanks for the quick response. 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. Thanks. -- Aaron M. Ucko, KB1CJC (amu at alum.mit.edu, ucko at debian.org) http://www.mit.edu/~amu/ | http://stuff.mit.edu/cgi/finger/?a...@monk.mit.edu -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
