Comment 18 for bug 294190

Revision history for this message
Andre (ajx) wrote :

I guess it is not wpa_supplicant's fault. On Intrepid a

ps -ef | grep wpa_suppli

reveals the start options:

/sbin/wpa_supplicant -u -f /var/log/wpa_supplicant.log

These are written in the file:
/usr/share/dbus-1/system-services/fi.epitest.hostap.WPASupplicant.service

I added a "-qq" here:
/sbin/wpa_supplicant -qq -u -f /var/log/wpa_supplicant.log

But even after wpa_supplicant has been restartet, syslog is dumped with these connection-state messages. So, I guess, it has got to be NetworkManager itself.