6f9099fa62
In case of unexpected failures of the services - such as an OOM - it shouldn't be necessary for an administrator to restart the service by hand (which is usually sufficient). Instead, this should happen automatically. Also, I decided to increase the interval between restart attempts from 100ms[1] to 10s for a small grace period as suggested by several online resources[2][3]. [1] See `systemd.service(5)` [2] https://it.megocollector.com/linux/create-systemd-services-for-atlassian-apps/ [3] https://anteru.net/blog/2017/jira-confluence-with-systemd-on-centos/ |
||
|---|---|---|
| .. | ||
| config | ||
| hardware | ||
| i18n/input-method | ||
| installer | ||
| misc | ||
| profiles | ||
| programs | ||
| security | ||
| services | ||
| system | ||
| tasks | ||
| testing | ||
| virtualisation | ||
| module-list.nix | ||
| rename.nix | ||