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 <philipp@redfish-solutions.com>

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

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
+}