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 <redacted>

diff --git a/admin/syslog-ng/Makefile b/admin/syslog-ng/Makefile
index b47151e4679ece9713d68fad7d4992b227ecc13a..50540d54e7820d6390472dca6e02f40c73e221c2 100644 (file)
--- 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 <josef.schlehofer@nic.cz>
 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 b68c6574f5bf9e6530f5d0623ed9a7ce040b4ff0..5ca2d2aa7f01a5b8c1260133c16581ce0f002d5e 100644 (file)
--- 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
+}