Hi,
On Sun, 04 Jan 2015 00:42:42 +0100 Bernhard Schmidt
<[email protected]> wrote:
> I suspect that this indeed a race between nslcd starting up and
> /etc/network/if-up.d/nslcd sending SIGUSR1 to the process. This sounds
> like
http://arthurdejong.org/git/nss-pam-ldapd/commit/?id=1d3b19b1ecd3b10f36e8925e8a752a28e3e74b56
> could help here. Unfortunately I wasn't able to reproduce the problem
> so testing the patch won't help.
No luck with this patch for me. Still getting the ‘unable to daemonize’
messages in the log. Of course it would be more helpful, if the nslcd
daemon would be able to give a better error code to systemd.
I have now switched over to the nslcd.service file from a Fedora 21
system (simply copied it to /etc/systemd/system) and have not had any
issues over the last couple of reboots.
$ systemctl cat nslcd.service
# /etc/systemd/system/nslcd.service
[Unit]
Description=Naming services LDAP client daemon.
After=syslog.target network.target named.service dirsrv.target
slapd.service
[Service]
Type=forking
PIDFile=/var/run/nslcd/nslcd.pid
ExecStart=/usr/sbin/nslcd
[Install]
WantedBy=multi-user.target
Cheers
/rike
--
To UNSUBSCRIBE, email to [email protected]
with a subject of "unsubscribe". Trouble? Contact [email protected]
