The default logging level for the CTRL-EVENT-SIGNAL-CHANGE message may be repeated many times and fill the log file or journal. For example https://bugzilla.redhat.com/show_bug.cgi?id=2309148 and the first few results from searching CTRL-EVENT-SIGNAL-CHANGE on the web contain various complaints and workarounds. Change the logging method to wpa_msg_ctrl to avoid sending frequent messages to the syslog but still allow the message to be consumed by control interface monitors. Signed-off-by: Kan-Ru Chen <kanru@xxxxxxxxxx> --- wpa_supplicant/events.c | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/wpa_supplicant/events.c b/wpa_supplicant/events.c index 5a1bc6d58..0a702ccc6 100644 --- a/wpa_supplicant/events.c +++ b/wpa_supplicant/events.c @@ -6766,7 +6766,7 @@ void wpa_supplicant_event(void *ctx, enum wpa_event_type event, data->eapol_rx.encrypted); break; case EVENT_SIGNAL_CHANGE: - wpa_msg(wpa_s, MSG_INFO, WPA_EVENT_SIGNAL_CHANGE + wpa_msg_ctrl(wpa_s, MSG_INFO, WPA_EVENT_SIGNAL_CHANGE "above=%d signal=%d noise=%d txrate=%lu", data->signal_change.above_threshold, data->signal_change.data.signal, -- 2.47.1 _______________________________________________ Hostap mailing list Hostap@xxxxxxxxxxxxxxxxxxx http://lists.infradead.org/mailman/listinfo/hostap
