I do not believe this is a good idea, as it may promote a crash loop, and cause other issues to occur. If DS crashes, we want to know about it, and we must let an administrator intervene.

Systemd will not loop forever, it has a limit.
We do want to know in engineering, but customers want to see automatic recovery when possible.

Please reconsider, at least for IPA, DS down means every other service we provide is also down and it is a major issue.

IPA can over-ride this with systemd drop ins if you wish, or by altering /etc/sysconfig/dirsrv-

However, I strongly recommend against this and it's usage with DS.

Finally, this issue can't be that big of a deal because it has been ignored for 2 years - I don't really think it's worth our time since no one has cared about it, not even enough to follow up.

Leaving this closed wontfix.

389-ds-base is moving from Pagure to Github. This means that new issues and pull requests
will be accepted only in 389-ds-base's github repository.

This issue has been cloned to Github and is available here:
- https://github.com/389ds/389-ds-base/issues/1107

If you want to receive further updates on the issue, please navigate to the github issue
and click on subscribe button.

Thank you for understanding. We apologize for all inconvenience.