On Mon, Apr 22, 2019 at 10:12:14AM +0200, Sven Eckelmann wrote:
The correct way to get a log of the activities of batman-adv is to use the standard kernel tracing infrastructure:
$ trace-cmd stream -e batadv:batadv_dbg
The batman-adv specific log file will be removed in the future when the debugfs is dropped. And even for kernels without tracing support, most of the functionality (except mac address to bat_hosts translation) can be replaced by a simple:
$ cat /sys/kernel/debug/batman_adv/bat0/log
Signed-off-by: Sven Eckelmann sven@narfation.org
The trace-cmd approach does not add/provide network namespace support, does it?
If we were removing "batctl log" now we would probably need to readd it later again when adding network namespace support, both for either a netlink or IPv6 node-local multicast approach, right [0]?
(Although for the IPv6 node-local multicast 'socat' for instance would work, too.)
[0]: 'Make "batctl log" usable with network namespaces' https://www.open-mesh.org/issues/339