From 387267814d0ec4a97a33fcdfe58f4f6cb23a54c9 Mon Sep 17 00:00:00 2001 From: Mike Perham Date: Wed, 8 Apr 2020 09:48:43 -0700 Subject: [PATCH] tweaks Mention `systemctl kill` and ease up on the watchdog a bit. --- examples/systemd/sidekiq.service | 5 +++-- 1 file changed, 3 insertions(+), 2 deletions(-) diff --git a/examples/systemd/sidekiq.service b/examples/systemd/sidekiq.service index ed5bf08ab..ce7286b5d 100644 --- a/examples/systemd/sidekiq.service +++ b/examples/systemd/sidekiq.service @@ -5,7 +5,7 @@ # Customize and copy this into /usr/lib/systemd/system (CentOS) or /lib/systemd/system (Ubuntu). # Then run: # - systemctl enable sidekiq -# - systemctl {start,stop,restart,reload} sidekiq +# - systemctl {start,stop,restart} sidekiq # # This file corresponds to a single Sidekiq process. Add multiple copies # to run multiple processes (sidekiq-1, sidekiq-2, etc). @@ -38,7 +38,7 @@ After=syslog.target network.target # Type=notify # If your Sidekiq process locks up, systemd's watchdog will restart it within seconds. -WatchdogSec=5 +WatchdogSec=10 WorkingDirectory=/opt/myapp/current # If you use rbenv: @@ -49,6 +49,7 @@ ExecStart=/usr/local/bin/bundle exec sidekiq -e production # use `systemctl reload sidekiq` to send the quiet signal to Sidekiq # at the start of your deploy process. +# Or you can use `systemctl kill -s TSTP sidekiq` ExecReload=/usr/bin/kill -TSTP $MAINPID User=deploy