Project

General

Profile

« Previous | Next » 

Revision 32f54190

Added by Adam Ruzicka over 5 years ago

Fixes #24927 - Fix sending signal after logrotate

The solution with using pkill was not ideal as pkill
would match the process it was meant to kill and the
shell running pkill as well. This could lead to
a situation where the shell would be killed first
and the signal would not be delivered to the intended
target process.

View differences:

packages/plugins/rubygem-smart_proxy_dynflow_core/logrotate.conf
compress
daily
postrotate
pkill --signal SIGUSR1 --full /usr/bin/smart_proxy_dynflow_core >/dev/null 2>&1 || true
/bin/systemctl kill --signal=SIGUSR1 --kill-who=main smart_proxy_dynflow_core >/dev/null 2>&1 || true
endscript
}
packages/plugins/rubygem-smart_proxy_dynflow_core/rubygem-smart_proxy_dynflow_core.spec
Summary: Core Smart Proxy Dynflow Service
Name: %{?scl_prefix}rubygem-%{gem_name}
Version: 0.2.0
Release: 3%{?foremandist}%{?dist}
Release: 4%{?foremandist}%{?dist}
Group: Development/Libraries
License: GPLv3
URL: https://github.com/theforeman/smart_proxy_dynflow
......
Requires: %{?scl_prefix_ror}rubygem(sqlite3)
Requires: %{?scl_prefix_ruby}ruby(release)
Requires: %{?scl_prefix_ruby}rubygems
Requires: /usr/bin/pkill
Requires(post): systemd-sysv
Requires(post): systemd-units
Requires(preun): systemd-units
......
%doc %{gem_instdir}/LICENSE
%changelog
* Wed Sep 12 2018 Adam Ruzicka <aruzicka@redhat.com> 0.2.0-4
- Send signal after logrotate with systemctl kill --kill-who=main
* Wed Sep 12 2018 Adam Ruzicka <aruzicka@redhat.com> 0.2.0-3
- Fix signal sending after logrotate

Also available in: Unified diff