From d93f5c2332be97ceb73984fd36911ed6f5b03f6f Mon Sep 17 00:00:00 2001
From: Arun Isaac
Date: Tue, 31 Jan 2023 00:23:48 +0000
Subject: issues: Clean up Unix socket when deployed with shepherd.

*
issues/tissue-does-not-clean-up-unix-socket-when-deployed-with-shepherd.gmi:
New issue.
---
 ...does-not-clean-up-unix-socket-when-deployed-with-shepherd.gmi | 9 +++++++++
 1 file changed, 9 insertions(+)
 create mode 100644 issues/tissue-does-not-clean-up-unix-socket-when-deployed-with-shepherd.gmi

(limited to 'issues')

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.
-- 
cgit v1.2.3