Timeline for How to configure systemd to kill and restart a daemon on reload?
Current License: CC BY-SA 3.0
Post Revisions
9 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Nov 5, 2017 at 15:47 | history | tweeted | twitter.com/ServerFault/status/927200631936503814 | ||
| May 24, 2016 at 23:22 | vote | accept | TomOnTime | ||
| Apr 3, 2016 at 19:30 | answer | added | TomOnTime | timeline score: 22 | |
| Apr 3, 2016 at 16:24 | vote | accept | TomOnTime | ||
| Apr 3, 2016 at 19:23 | |||||
| Apr 3, 2016 at 16:24 | answer | added | TomOnTime | timeline score: 3 | |
| Mar 31, 2016 at 22:44 | comment | added | Michael Hampton | I'm sure an answer might help someone, so I did upvote the question. I'm just not sure that this is a common use case. Having used systemd for five years or so, almost from the day it was unleashed upon the world, this is the first time I can recall hearing about anyone attempting this sort of scenario. It's possible I am misunderstanding something because of missing details. | |
| Mar 31, 2016 at 22:33 | comment | added | TomOnTime | Thanks @MichaelHampton, but this isn't a situation where I can rewrite the program. I appreciate your helpful suggestion. That said, i'm sure this is a common systemd use-case and a canonical answer might help a lot of people. | |
| Mar 31, 2016 at 18:24 | comment | added | Michael Hampton | Does this really need to be shoehorned into reload, where it doesn't quite exactly fit? Can you not make the daemon behave sensibly? | |
| Mar 31, 2016 at 15:58 | history | asked | TomOnTime | CC BY-SA 3.0 |