Lars Hanke <deb...@lhanke.de> writes: > I ran into this issue recently and filed this bug to nslcd: #787020 and > #766606. So it persists for more than 2 years and made it across Debian > release. I use k5start / nslcd to authenticate to samba4 AD. I'm > surprised that it should be such a rare scenario.
> The situation actually looks quite wiered. Retrying after login always > succeeds. Retrying in /etc/rc.local or by cron @reboot in general never > works. On a i686 system running Wheezy it always succeeds. So if timing > is the root of all evil, the required delay seems to be quite long. > Could you please try to co-operate with Arthur to hunt down and > eventually fix the issue? There isn't anything to hunt down -- I know what the problem is, which is that if the initial authentication fails, k5start will exit, but it should keep running and keep retrying. I think this is already fixed in Git, and just requires a new release. However, with a job change that's been interesting but much more time-consuming (and less focused on Kerberos) than I had expected, I've had almost no time to work on k5start. I still hope to get a new release out with this fix, but I don't know when. Sorry. :/ -- 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
