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

[Kel Modderman]

On Tuesday 04 August 2009 22:34:54 Michael Biebl wrote:
> Package: wpasupplicant
> Version: 0.6.9-3
> Severity: normal
> 
> Hi,
> 
> I'm using wpa_supplicant via NetworkManager (autostarted by dbus).
> I get a lot (multiple hundreds) of those messages in my /var/log/syslog:
> 
> Aug  4 02:24:26 pluto wpa_supplicant[2781]: CTRL-EVENT-SCAN-RESULTS
> Aug  4 02:25:06 pluto wpa_supplicant[2781]: CTRL-EVENT-SCAN-RESULTS
> Aug  4 02:26:06 pluto wpa_supplicant[2781]: CTRL-EVENT-SCAN-RESULTS
> Aug  4 02:27:26 pluto wpa_supplicant[2781]: CTRL-EVENT-SCAN-RESULTS
> Aug  4 02:29:06 pluto wpa_supplicant[2781]: CTRL-EVENT-SCAN-RESULTS
> Aug  4 02:31:06 pluto wpa_supplicant[2781]: CTRL-EVENT-SCAN-RESULTS
> ....
> 
> Those messages don't look that terribly important to me and should
> probably only emitted in debug mode so they don't spam the syslog.

They are required by wpa_ctrl UNIX control socket clients to be notified
about new scan results (eg. wpa_gui), i *think*.
iirc, there is a launchpad bug for this too, i did patch wpa_supplicant
as per that bug to reduce the priority level of the scan-results event
to debug level, and wpa_gui seemed to fail to refresh scan results.

Maybe there is a way to special escape them from being logged, while
still serving purpose. Need to be forwarded upstream for discussion i guess.

Thanks, Kel.