Control: found -1 nss-pam-ldapd/0.9.1-1 Control: tags + pending On Mon, 2015-04-13 at 15:36 +0200, Bernhard Schmidt wrote: > I still think it is caused by a race between the ifupdown trigger and > nslcd startup.
Thanks for prodding me about this. I've spent some more time trying to track this down and I managed to find a reproducible scenario with some tweaking (introducing sleeps at strategic places in the code and keep firing signals at nslcd). The problem was caused by a race condition in the start-up code regarding signal handling. It should be fixed in: http://arthurdejong.org/git/nss-pam-ldapd/commit/?id=530cc24c83dd5d2d347acb40d64c3ae06a43a293 A work-around for people experiencing this issue would be to comment out the kill-line in /etc/network/if-up.d/nslcd. Thanks, -- -- arthur - adej...@debian.org - http://people.debian.org/~adejong --
signature.asc
Description: This is a digitally signed message part
