summaryrefslogtreecommitdiff
path: root/issues/tissue-does-not-clean-up-unix-socket-when-deployed-with-shepherd.gmi
diff options
context:
space:
mode:
Diffstat (limited to 'issues/tissue-does-not-clean-up-unix-socket-when-deployed-with-shepherd.gmi')
-rw-r--r--issues/tissue-does-not-clean-up-unix-socket-when-deployed-with-shepherd.gmi9
1 files changed, 9 insertions, 0 deletions
diff --git a/issues/tissue-does-not-clean-up-unix-socket-when-deployed-with-shepherd.gmi b/issues/tissue-does-not-clean-up-unix-socket-when-deployed-with-shepherd.gmi
new file mode 100644
index 0000000..90092e6
--- /dev/null
+++ b/issues/tissue-does-not-clean-up-unix-socket-when-deployed-with-shepherd.gmi
@@ -0,0 +1,9 @@
+# tissue does not clean up Unix socket when deployed with shepherd
+
+* tags: bug
+
+When deployed with shepherd, and stopped using something like herd stop tissue, the tissue web server does not clean up its Unix socket. This means the next attempt to start tissue fails since the Unix socket file exists already.
+
+However, when tissue-web is run on the command-line and terminated with a Ctrl-C (SIGINT), it cleans up its Unix socket correctly.
+
+This issue is likely because tissue is not handling the SIGTERM signal correctly.