[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index][Old Index]
Re: kern/50019: bmon(1) shows tap(4) interface name with garbage at the end
On Thu, Jul 02, 2015 at 11:30:01AM +0000, Martin Husemann wrote:
> The following reply was made to PR kern/50019; it has been noted by GNATS.
> From: Martin Husemann <martin%duskware.de@localhost>
> To: Dominik Bialy <dmb%yenn.ulegend.net@localhost>
> Cc: gnats-bugs%NetBSD.org@localhost
> Subject: Re: kern/50019: bmon(1) shows tap(4) interface name with garbage at the end
> Date: Thu, 2 Jul 2015 13:29:00 +0200
> On Thu, Jul 02, 2015 at 12:39:49PM +0200, Dominik Bialy wrote:
> > It might be that this is a bug in bmon, although it shows up only
> > on tap(4) interfaces in NetBSD.
> ifconfit -a
> show the name properly? What API is bmon using to query the names?
Yes, ifconfig -a shows `tap0' properly.
It uses sysctl interface.
In `sysctl -a' `tap0' looks OK, also. So it seems you were right :)
> You are talking about this one?
Maybe... (sorry, only w3m at hand, and didn't look deeply into the github
page.) Although in pkgsrc bmon is at version 2.0.1. This looks like
> > If you are sure I made a mistake and it's a bug in that software,
> > feel free to close the PR.
> No idea yet, but a non-terminated string where the spec requires a null
> terminated one would likely cause a lot more fallout, so I'd be
> slightly suprised.
> (side note: should there be a pkgsrc for it?)
It is in pkgsrc net/bmon, maybe we just need an update.
The Underlegend Networks' Free Shells -- http://www.ulegend.net/
Main Index |
Thread Index |