Log filled with antenna switching lines when no antenna switching is available or wanted [fix 1.672]

F4VTQ

I just updated to the last release and now this in the log :

Wed Apr 17 15:05:52 00:09:29.281 01234567  3    ant_switch rx3 antsw_AntennasAre=

Wed Apr 17 15:05:52 00:09:29.385 01234567   4   ant_switch rx4 antsw_AntennasAre=

Wed Apr 17 15:05:52 00:09:29.386 01234567   5   ant_switch rx5 antsw_AntennasAre=

Wed Apr 17 15:05:52 00:09:29.386 01234567    6  ant_switch rx6 antsw_AntennasAre=

Wed Apr 17 15:05:52 00:09:29.386 01234567    7  ant_switch rx7 antsw_AntennasAre=

Wed Apr 17 15:05:54 00:09:30.802 01234567      ant_switch_admin_msgs: <ADM antsw_GetBackends>

Wed Apr 17 15:05:54 00:09:31.014 01234567      ant_switch_admin_msgs: <ADM antsw_GetInfo>

Wed Apr 17 15:05:54 00:09:31.014 01234567      ant_switch ADM antsw_GetInfo antsw.backend_s=No

Wed Apr 17 15:05:55 00:09:32.219 01234567      ant_switch_admin_msgs: <ADM antsw_notify_users>

Wed Apr 17 15:05:55 00:09:32.219 01234567      ant_switch ADM antsw_notify_users

Wed Apr 17 15:05:55 00:09:32.219 01234567 0     ant_switch rx0 antsw_AntennasAre=

Can that kind of unneeded activity be switched off somehow ? I only find a select drop down on the antenna switch page but not a 'set inactive' or so.

Thanks

Erwin

jks

A couple of things:

• Remember that if the message seen in the admin "log" tab doesn't contain an "L" before the message it is not being recorded in the Linux/Debian syslog (the one that takes up filesystem space).
• Those messages are in there for now while any residual bugs in the new antenna switch code get fixed. I'll remove them in a later release. They've already been helpful as there are problems (as I expected there would be).