syslog-ng: restore service "reload" to actually working
Commit44a16ca
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> (cherry picked from commitc27f4ca53b
)
This commit is contained in:
parent
0e80f0486b
commit
64ebad3fd9
1 changed files with 4 additions and 0 deletions
|
@ -11,3 +11,7 @@ start_service() {
|
||||||
procd_set_param command /usr/sbin/syslog-ng --foreground
|
procd_set_param command /usr/sbin/syslog-ng --foreground
|
||||||
procd_close_instance
|
procd_close_instance
|
||||||
}
|
}
|
||||||
|
|
||||||
|
reload_service() {
|
||||||
|
/usr/sbin/syslog-ng-ctl reload
|
||||||
|
}
|
||||||
|
|
Loading…
Reference in a new issue