On Monday, 22 April 2019 11:20:48 CEST Linus Lüssing wrote:
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 trace-cmd approach does not add/provide network namespace support, does it?
Afaik, not at the moment.
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.)
I am rather sure that we shouldn't add the namespace specific logs in batman- adv via a batadv specific new infrastructure. Sounds like horrible hacks which we shouldn't even try to upstream.
Kind regards, Sven