From 4d8561aa0923b26bb1355923753ec8affee7388c Mon Sep 17 00:00:00 2001 From: mattie47 <4696925+mattie47@users.noreply.github.com> Date: Mon, 15 Jan 2018 08:47:28 +1300 Subject: fix: Allow Oxidized service to be stopped from services. (#1144) There is an issue with oxidized and correctly terminatating when a user stops the service. Unfortunately the root cause of this issue has yet to be identified, and it may have to do with specific versions of Ruby gems. As such, the workaround is to use a SIGKILL to kill the oxidized/puma service instead of a SIGINIT. Note: This does not solve the issue with manually starting the oxidized daemon and using Ctrl + c to stop it. The solution here is to then press Ctrl + Z, then manually "kill -9 ". --- extra/oxidized.service | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/extra/oxidized.service b/extra/oxidized.service index e474608..ce1b1a3 100644 --- a/extra/oxidized.service +++ b/extra/oxidized.service @@ -10,7 +10,7 @@ Wants=network-online.target [Service] ExecStart=/usr/local/bin/oxidized User=oxidized -KillSignal=SIGINT +KillSignal=SIGKILL [Install] WantedBy=multi-user.target -- cgit v1.2.1