All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Linus Lüssing" <linus.luessing@c0d3.blue>
To: The list for a Better Approach To Mobile Ad-hoc Networking
	<b.a.t.m.a.n@lists.open-mesh.org>
Subject: Re: [B.A.T.M.A.N.] [PATCH] batctl: Drop log subcommand
Date: Mon, 22 Apr 2019 11:20:48 +0200	[thread overview]
Message-ID: <20190422092048.GG6201@otheros> (raw)
In-Reply-To: <20190422081214.8481-1-sven@narfation.org>

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

  reply	other threads:[~2019-04-22  9:20 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-04-22  8:12 [B.A.T.M.A.N.] [PATCH] batctl: Drop log subcommand Sven Eckelmann
2019-04-22  9:20 ` Linus Lüssing [this message]
2019-04-22  9:30   ` Sven Eckelmann

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20190422092048.GG6201@otheros \
    --to=linus.luessing@c0d3.blue \
    --cc=b.a.t.m.a.n@lists.open-mesh.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.