I’ve implemented this solution in my environment, with some tweaks and modifications to give me log output for the calls to various scripts & compiled code. It works well… until… launchd becomes stale, and no longer has access to the user’s kerberos ticket. Ie; If I have a user that logs in, then stays logged in overnight, they can no longer print.
After troubleshooting, I find that if I run the user_kprintd (daemon) as the user, the printing works fine. But not if I kill the existing instance of user_kprintd, which is then respawned by launchd. I figure this is because the launchd is ‘stale’ and no longer has access to the current user’s environment for the kerberos ticket.
Has anyone else run into this issue? Not that it matters with Leopard right around the corner. But just curious.
-Josh
Recent Comments