Timeline for De-daemonizing an existing service
Current License: CC BY-SA 3.0
3 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Jul 6, 2016 at 17:21 | comment | added | Gilles 'SO- stop being evil' | @hheimbuerger Namespaces nest, so there's nothing about being in a Docker container that would make it harder to use a namespace. Whatever method you choose, how the helper script works may matter: if the helper script itself is doing the daemonizing, it's a different problem. Even if the helper script merely runs the daemon binary, but then does other things, some solutions will cause those other things to be done when the daemon exits, others won't. | |
| Jul 6, 2016 at 11:09 | comment | added | hheimbuerger | It's not necessarily a binary, and even if it is is launched by a complex init script which I don't want to modify (because it auto-updates every week) and which I don't want to make assumptions of, i.e. that it launches a certain executable at its core (again, because that might be different in the next week). The PID namespacing is interesting, although I don't yet quite understand whether I can do that inside a Docker container. I was hoping that there's a helper tool which I can just hand the initialization script and which does the de-daemonizing for me. | |
| Jun 30, 2016 at 23:53 | history | answered | Gilles 'SO- stop being evil' | CC BY-SA 3.0 |