The wpa_supplicant control socket might reply with "FAIL-BUSY" when
attempting to start a scan while another scanning process is already
running, back out early in this case.
Signed-off-by: Jo-Philipp Wich <jo@mein.io>
/* is another unrelated event, retry */
tries--;
}
+
+ /* got a failure reply */
+ else if (!strcmp(reply, "FAIL-BUSY\n"))
+ {
+ break;
+ }
}
/* receive and parse scan results if the wait above didn't time out */