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 <git@bitsofnetworks.org>

diff --git a/babeld/files/babeld.init b/babeld/files/babeld.init
index 416bbe4028daf91a0c9068214e7331f4f4460c21..def90b23e71bd3f8c990f5240efdfbe0531fbaa8 100755 (executable)
--- 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