Hector Palacios 505eb19aa4 hostapd: let start-stop-daemon create PID and background process ... The current script cannot launch the hostapd twice (for dual HostAP mode) because start-stop-daemon finds an already existing PID for hostapd after running the first instance. The solution is: - Do not launch the hostapd in background (so that it does not fork the process, which assigns a different PID) - Use -b option of start-stop-daemon so that it launches the daemon in the background. - Let start-stop-daemon create the PID (since the hostapd will not fork now this PID will match the hostapd process, allowing to kill it later) This solution also hides the hostapd log messages that appeared before. Signed-off-by: Hector Palacios <hector.palacios@digi.com> https://jira.digi.com/browse/DEL-4045		2017-04-07 12:28:14 +02:00
..
hostapd	hostapd: let start-stop-daemon create PID and background process	2017-04-07 12:28:14 +02:00
hostapd_%.bbappend	hostapd: parametrize hostapd init script per interface	2017-04-05 18:15:27 +02:00