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 it will continue in that function is if the exit status for both start-stop-daemon commands is 0. then, regardless of any of that, the script exits 0 no matter what, so systemd never knows something didn't go right. it's left thinking the service is running, but it's not. when the init script is changed to exit with the exit status of dkim, then systemd knows what's going on and handles the outcome as expected. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1452538 Title: opendkim does not start properly when ldap server can't be contacted To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1452538/+subscriptions -- ubuntu-bugs mailing list [email protected] https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
