Timeline for Systemd won't respawn processes
Current License: CC BY-SA 4.0
8 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| May 22, 2020 at 7:09 | vote | accept | annahri | ||
| May 5, 2020 at 19:24 | comment | added | annahri | @JdeBP My initial thought of using systemd is simply to automatically starts the script in case of system reboots. After reading this, I think it's true that the "ImportantScript" is a Poor Man's Daemon. Feels bad haha | |
| May 5, 2020 at 19:10 | answer | added | Chris Down | timeline score: 6 | |
| May 5, 2020 at 19:05 | comment | added | annahri | @JdeBP I was looking up on google about systemd House of Horror and I found your articles. I'm not so familiar with systemd yet, I hope you can give me insights. Please see my edit. | |
| May 5, 2020 at 19:05 | history | edited | annahri | CC BY-SA 4.0 |
Adding additional info
|
| May 5, 2020 at 9:49 | comment | added | JdeBP |
It's a good bet, given the start and stop verbs, that "importantScript" is far from important and is more likely a Poor Man's Dæmon Supervisor and Bad Logger that is in fact getting in the way. For best results, you should tell people how your real dæmon is actually run, in the depths of that script. Only with that information can one construct a service unit that isn't a systemd House of Horror entry.
|
|
| May 5, 2020 at 6:12 | comment | added | DevilaN |
rc scripts are only responsible for starting services and not maintaining it running. You should look forward onto something like supervisor daemon with proper config.
|
|
| May 5, 2020 at 5:06 | history | asked | annahri | CC BY-SA 4.0 |