I think a database-like service having such a restart configuration should be a local decision by each administrator. I fear data could be corrupted, for example, if the crash was caused by a bug, and further restarts could make the problem worse.
What I do agree with is that openldap should migrate to a systemd service, away from sysv. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to openldap in Ubuntu. https://bugs.launchpad.net/bugs/1838380 Title: slapd does not automatically restart on failure Status in openldap package in Ubuntu: Confirmed Bug description: Slapd does not restart after a failure. Slapd package does not include systemd unit file at all, only init.d script. Makes sense to make a unitfile with a Restart=on-failure option. $ lsb_release -rd Description: Ubuntu 16.04.5 LTS Release: 16.04 $ apt-cache policy slapd slapd: Installed: 2.4.42+dfsg-2ubuntu3.3 Candidate: 2.4.42+dfsg-2ubuntu3.5 Version table: 2.4.42+dfsg-2ubuntu3.5 500 500 http://nl.archive.ubuntu.com/ubuntu xenial-updates/main amd64 Packages *** 2.4.42+dfsg-2ubuntu3.3 100 100 /var/lib/dpkg/status 2.4.42+dfsg-2ubuntu3.2 500 500 http://security.ubuntu.com/ubuntu xenial-security/main amd64 Packages 2.4.42+dfsg-2ubuntu3 500 500 http://nl.archive.ubuntu.com/ubuntu xenial/main amd64 Packages affects ubuntu/openldap To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/openldap/+bug/1838380/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : [email protected] Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
