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>
17 lines
302 B
Bash
17 lines
302 B
Bash
#!/bin/sh /etc/rc.common
|
|
# Copyright (C) 2006-2019 OpenWrt.org
|
|
|
|
START=50
|
|
|
|
USE_PROCD=1
|
|
|
|
start_service() {
|
|
[ -f /etc/syslog-ng.conf ] || return 1
|
|
procd_open_instance
|
|
procd_set_param command /usr/sbin/syslog-ng --foreground
|
|
procd_close_instance
|
|
}
|
|
|
|
reload_service() {
|
|
/usr/sbin/syslog-ng-ctl reload
|
|
}
|