Thinking more about the way the sasl_mech and krb5_ccname options were
handled, I saw that the logic in the nslcd-k5start file wasn't very good
--we should only be looking for the kinit and k5start binaries if the
user enabled Kerberos, either through the defaults file override, or
with the nslcd.conf settings. Rewriting to account for this cleans up
the logic quite a bit.

I'm struggling with some very odd behavior (calling kinit and k5start in
the same script stanza fails if the job is started as a pre-condition
for some other job, but works fine if the job is started directly), but
expect to submit a revised debdiff in the next day or so.

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/806761

Title:
  Feature Request: Upstart scripts for nslcd

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/nss-pam-ldapd/+bug/806761/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

Reply via email to