diff options
| author | mattie47 <4696925+mattie47@users.noreply.github.com> | 2018-01-15 08:47:28 +1300 |
|---|---|---|
| committer | Neil Lathwood <neil@lathwood.co.uk> | 2018-01-14 19:47:28 +0000 |
| commit | 4d8561aa0923b26bb1355923753ec8affee7388c (patch) | |
| tree | 5edc01f056521f4f12e232cba3c4b189e4240d61 /extra | |
| parent | 3d140e81a8b40ecb63704523e78bf46455b9f238 (diff) | |
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 <PID>".
Diffstat (limited to 'extra')
| -rw-r--r-- | extra/oxidized.service | 2 |
1 files changed, 1 insertions, 1 deletions
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 |