From fd424268ba0945ab6647d1fbb1674b1c85c59f82 Mon Sep 17 00:00:00 2001 From: Baptiste Jonglez Date: Mon, 9 Jan 2017 15:42:58 +0100 Subject: [PATCH 1/1] babeld: Log to the system log instead of logging to a file This avoids running out of flash or RAM space if babeld logs too much. The system log is stored on RAM by default and has a controlled size. It is still possible to tell babeld to log to a file, by using the following in /etc/config/babeld: config general option log_file "/var/log/babeld.log" Signed-off-by: Baptiste Jonglez --- babeld/files/babeld.init | 4 +++- 1 file changed, 3 insertions(+), 1 deletion(-) diff --git a/babeld/files/babeld.init b/babeld/files/babeld.init index 416bbe4..def90b2 100755 --- a/babeld/files/babeld.init +++ b/babeld/files/babeld.init @@ -237,7 +237,9 @@ start_service() { config_foreach babel_filter filter procd_open_instance # Using multiple config files is supported since babeld 1.5.1 - procd_set_param command /usr/sbin/babeld -L /var/log/babeld.log -I "" -c "$OTHERCONFIGFILE" -c "$CONFIGFILE" + procd_set_param command /usr/sbin/babeld -I "" -c "$OTHERCONFIGFILE" -c "$CONFIGFILE" + procd_set_param stdout 1 + procd_set_param stderr 1 procd_set_param file "$OTHERCONFIGFILE" "$CONFIGFILE" procd_set_param respawn procd_close_instance -- 2.35.1