26 Mar
2017
26 Mar
'17
8:50 a.m.
On 23.03.2017 20:13, Pau wrote:
BTW @Axel do not forget to also apply this patch (and
the previous ones)
to bmx7.
The excessive-logging one is not needed for bmx7 (IIDs do not jump in bmx7).
The --configSync one for bmx7 is now in bmx7 branch tip:
https://github.com/axn/bmx6/commit/64e29020ac683b246e28094742838ff39cb7ee80
On 23/03/17 20:10, Pau wrote:
> @Axel, should I update the openwrt-routing feed to include this patch
> into official LEDE source?
Yes, that would be nice. Maybe also update bmx7 package then.
thx
/axel
On 22/03/17 08:34, Axel Neumann wrote:
_______________________________________________
lime-dev mailing list
lime-dev(a)lists.libremesh.org
https://lists.libremesh.org/mailman/listinfo/lime-dev
_______________________________________________
lime-dev mailing list
lime-dev(a)lists.libremesh.org
https://lists.libremesh.org/mailman/listinfo/lime-dev
>
> how exactly does --dbgMuteTimeout work?
It mutes messages that are logged with dbgf_mute() function after having
appeared twice for the amount of ms you specified with --dbgMuteTimeout.
Let me try better:
It mutes (suspends) log messages for the amount of ms you specified with
--dbgMuteTimeout.
But only those that were internally called via dbgf_mute() function and
only if the to-be-logged string happened more than twice within the
given timeout.
So --dbgMuteTimeout=3600000 should log muted messages at most twice per
hour.
The log message you complain about was not logged
with the dbgf_mute()
function and was therefore always logged.
>
> and how can we prevent those messages from showing up in the logs?
You could only change the code, or update to the latest bmx6
master-branch version. It contains below patch :-)
https://github.com/axn/bmx6/commit/4016a1980d900309771e432d1f7c741d6c48d477
cheers too
/axel
>
> cheers!!
>
_______________________________________________
lime-dev mailing list
lime-dev(a)lists.libremesh.org
https://lists.libremesh.org/mailman/listinfo/lime-dev