#20623: hostapd: no logging of wpa_printf messages
-----------------------+------------------------
  Reporter:  rmilecki  |      Owner:  developers
      Type:  defect    |     Status:  reopened
  Priority:  normal    |  Milestone:
 Component:  packages  |    Version:  Trunk
Resolution:            |   Keywords:
-----------------------+------------------------

Comment (by rmilecki):

 I did a bit more of hostapd messages testing and there is something
 interesting I found. Every `wpa_printf(MSG_ERROR, "...");` executed
 '''before''' calling `eloop_run();` '''appears''' in the syslog.

 Calls to `wpa_printf` executed after that are harder to predict.
 - Adding `wpa_printf` to `hostapd_periodic` never results in message
 appearing in a syslog
 - Message from `wpa_printf` placed right after `eloop_run();` call is
 silent as well.
 - On the other hand I can see output of `wpa_printf` called in
 `hostapd_flush_old_stations`.

 Maybe it's only about ''eloop'' callbacks? Maybe they are executed from
 different process (''eloop'' process?) and `netifd` doesn't dups this
 process's stdout/stderr?

--
Ticket URL: <https://dev.openwrt.org/ticket/20623#comment:5>
OpenWrt <http://openwrt.org>
Opensource Wireless Router Technology
_______________________________________________
openwrt-tickets mailing list
[email protected]
https://lists.openwrt.org/cgi-bin/mailman/listinfo/openwrt-tickets

Reply via email to