Hello Jerome,
Ok, got it. logread is started without the -h option so the remote syslogd may or may not cope very well and in the ubus call log write_ext originating messages it doesn't. Result: rsyslogd clutters the log directory with a lot of seemingly unrelated files which are a pain to reconcile.
Here is a patch against /etc/init.d/log it adds the -h option to logread. Now rsyslogd coalesces all the RUTX11 log messages in one file only. Could you insure that it will be included in the next release ?
===================================================================
--- log-old 2021-02-09 15:48:12.814407941 +0100
+++ log 2021-02-09 16:04:24.616430206 +0100
@@ -69,9 +69,10 @@
}
[ "${log_remote}" -ne 0 ] || return
[ -z "${log_ip}" ] && return
+ [ -z "${log_hostname}" ] && log_hostname=$(cat /proc/sys/kernel/hostname)
procd_open_instance
- procd_set_param command "$PROG" -f -r "$log_ip" "${log_port}" -p "$pid_file"
+ procd_set_param command "$PROG" -f -h "$log_hostname" -r "$log_ip" "${log_port}" -p "$pid_file"
case "${log_proto}" in
"udp") procd_append_param command -u;;
"tcp") [ "${log_trailer_null}" -eq 1 ] && procd_append_param command -0;;
===================================================================
Regards,
