From c27f4ca53b231823d4298ab976d0a64ed61dfa99 Mon Sep 17 00:00:00 2001 From: Philip Prindeville Date: Tue, 5 May 2020 15:00:50 -0600 Subject: [PATCH] syslog-ng: restore service "reload" to actually working Commit 44a16ca broke syslog-ng such that it no longer works with logrotate, for example. Yes, you can manually stop and start the service, but (1) you shouldn't have to and (2) it creates a window where you potentially lose messages if the syslog UDP socket overruns. Signed-off-by: Philip Prindeville --- admin/syslog-ng/Makefile | 2 +- admin/syslog-ng/files/syslog-ng.init | 4 ++++ 2 files changed, 5 insertions(+), 1 deletion(-) diff --git a/admin/syslog-ng/Makefile b/admin/syslog-ng/Makefile index b47151e467..50540d54e7 100644 --- a/admin/syslog-ng/Makefile +++ b/admin/syslog-ng/Makefile @@ -2,7 +2,7 @@ include $(TOPDIR)/rules.mk PKG_NAME:=syslog-ng PKG_VERSION:=3.26.1 -PKG_RELEASE:=1 +PKG_RELEASE:=2 PKG_MAINTAINER:=Josef Schlehofer PKG_LICENSE:=LGPL-2.1-or-later GPL-2.0-or-later diff --git a/admin/syslog-ng/files/syslog-ng.init b/admin/syslog-ng/files/syslog-ng.init index b68c6574f5..5ca2d2aa7f 100644 --- a/admin/syslog-ng/files/syslog-ng.init +++ b/admin/syslog-ng/files/syslog-ng.init @@ -11,3 +11,7 @@ start_service() { procd_set_param command /usr/sbin/syslog-ng --foreground procd_close_instance } + +reload_service() { + /usr/sbin/syslog-ng-ctl reload +} -- 2.30.2