Package: nslcd Version: 0.9.4-3+deb8u2 As noted in https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=851134#5,
"When it crashes, systemd does not automatically restart the process, which may be a separate issue." I can confirm this. I've seen nslcd crash (with different symptoms than in #851134: my failure was May 26 08:49:29 HOSTNAME kernel: [ 68.374501] nslcd[1214]: segfault at 10 ip 00007fc34d890234 sp 00007fc34a0f3140 error 4 in libpthread-2.19.so[7fc34d886000+18000] ) and not restart. systemctl showed: * nslcd.service - LSB: LDAP connection daemon Loaded: loaded (/etc/init.d/nslcd) Active: active (exited) since Fri 2017-05-26 08:49:29 CEST; 1 weeks 0 days ago Process: 1069 ExecStart=/etc/init.d/nslcd start (code=exited, status=0/SUCCESS) May 26 08:49:25 HOSTNAME nslcd[1091]: version 0.9.4 starting May 26 08:49:29 HOSTNAME nslcd[1091]: accepting connections May 26 08:49:29 HOSTNAME nslcd[1069]: Starting LDAP connection daemon: nslcd. May 26 08:49:29 HOSTNAME systemd[1]: Started LSB: LDAP connection daemon. This reminds me of bugs #827444 and #807132. A similar solution (overriding the systemd unit generator's choice of RemainAfterExit=yes) may apply (I haven't tested this yet).
