@Scott: bug 1447807 is different.
Ben Thielsen has it exactly right: the init.d script entirely ignores
the return value of start-stup-daemon. It neither has an upstart job nor
systemd unit, so systemd and upstart call the init.d script and rely on
its exit code.
** Package changed: systemd
thanks for this. i'd tried LDAPSoftStart, which didn't work, missing
that it had been renamed. i've added SoftStart yes to the config, but
the behavior seems to be the same.
i can corroborate that this seems new with 15.04/systemd. another older
system like yours works ok.
--
You received
I can't replicate this on an older release with upstart instead of
systemd.
service opendkim start
Starting OpenDKIM: opendkim: /etc/opendkim.conf:
ldap://192.0.2.1/ou=people,dc=example,dc=com?DKIMSelector?sub?(DKIMIdentity=$d):
dkimf_db_open(): Can't contact LDAP server
opendkim.
# ps -AF|grep
some additional detail regarding SoftStart - it seems to not be working
right [systemd issues excluded]:
egrep -v '(^[[:space:]]*#|^[[:space:]]*$)' opendkim.conf
Syslog yes
SyslogSuccess yes
LogWhy yes
UMask
it seems like in addition to the softstart issue, the init script is in
need of some attention?
it runs start-stop-daemon to check the config and start the process, but
both commands are or'd with a return 1 or return 2. the check to handle
exit status 78 can never happen, because the only way
5 matches
Mail list logo
