summaryrefslogtreecommitdiff
path: root/wiki/devops/self-daemonization-sucks.md
diff options
context:
space:
mode:
authorOwen Jacobson <owen.jacobson@grimoire.ca>2014-03-14 14:31:28 -0400
committerOwen Jacobson <owen.jacobson@grimoire.ca>2014-03-14 14:31:28 -0400
commit4a563ed3f3a05b4b4c99941d69a2350fcd0f3eae (patch)
treecac3ee7f40ffbbaa01b2ac6b09c5e3219926d70b /wiki/devops/self-daemonization-sucks.md
parentac29facf031f7834be82b0599e28da266f819ae3 (diff)
Oh man, thanks systemd docs.
Diffstat (limited to 'wiki/devops/self-daemonization-sucks.md')
-rw-r--r--wiki/devops/self-daemonization-sucks.md3
1 files changed, 3 insertions, 0 deletions
diff --git a/wiki/devops/self-daemonization-sucks.md b/wiki/devops/self-daemonization-sucks.md
index 6560904..73bc784 100644
--- a/wiki/devops/self-daemonization-sucks.md
+++ b/wiki/devops/self-daemonization-sucks.md
@@ -51,6 +51,9 @@ given the individual interfaces' relative simplicity:
* Daemons must ensure that all of the above steps happen in signal-safe ways,
so that a daemon can be shut down sanely even if it's still starting up
+See [this list](http://www.freedesktop.org/software/systemd/man/daemon.html)
+for a longer version. It's worse than you think.
+
All of this gets even more complicated if the daemon has its own child
processes, a pattern common to network services. Naturally, a lot of daemons
in the real world get some of these steps wrong.