[pkg-wpa-devel] Bug#539915: wpasupplicant: Spams syslog with CTRL-EVENT-SCAN-RESULTS

[tytso at mit.edu]

On Sun, Nov 22, 2009 at 11:29:28AM +1000, Kel Modderman wrote:
> > It's gross as all
> > heck that the wpa_gui is using a facility originally from wpa_debug.c
> > to communicate with wpa_supplicant.  That's an upstream problem, yes
> > and they ought to be ashamed of themselves.  :-)
> 
> No idea why anyone needs to be ashamed about that.

Well, my sense of aesthetics are violated when a logging channel and a
control channel are slammed on top of each other.  Arguably wpa_gui
should have used a separate way of communicating with wpa_supplicant
other than specially formatted message in-band in the logging channel.
It just seems like a gross kludge to me, and wpa_msg_ctrl() is piling
a kludge on top of a kludge.  It'll work for now, but it's not what I
would call a clean design.  But whatever; different developers will
have different standards of architectural cleanliness than others....

> Committed [2] as a round up of patches which reduce too frequent
> messages from appearing in logs and the QT frontend.
> 
> [2] http://lists.alioth.debian.org/pipermail/pkg-wpa-devel/2009-November/002383.html

Cools, thanks.  What was the Ubuntu Launchpad bug # that you mentioned
where this came up?  It would be nice to mention this to the Ubuntu
folks to see if they would be interested in picking this up as a
bugfix for Karmic.  The syslog spam really was painfully annoying, and
chewed up a lot of SSD write endurance that I really would have rather
not have burned up.

						- Ted