[LEDE-DEV] dnsmasq sometimes fails to start on 17.01.0

[Yousong Zhou]

>From the log, there are at least 4 runs of /etc/init.d/dnsmasq

This is "/e/c/dnsmasq boot" and returns immediately because the script skips
this phase and the dnsmasq service is expected to be brought up by interface
trigger events

	root at coco:~# logread | grep dns
	Wed Mar 22 18:25:56 2017 user.notice root: guidebug dnsmasq init
	Wed Mar 22 18:25:56 2017 user.notice root: guidebug dnsmasq boot
	Wed Mar 22 18:25:56 2017 user.notice root: guidebug dnsmasq startsrv 1,
	Wed Mar 22 18:25:56 2017 user.notice root: guidebug dnsmasq srvtrg

This one I do not have much clue about

	Wed Mar 22 18:25:57 2017 user.notice root: guidebug dnsmasq init

This one was brought up by the interface trigger event.  Your log stopped at
"wait 18" without "wait 16" because the service_triggers call in the
/e/c/dnsmasq has set the timeout of event handling to be 2000ms.  That's how
the logger and sleep call were impeding the process

	Wed Mar 22 18:26:06 2017 user.notice root: guidebug dnsmasq init
	Wed Mar 22 18:26:06 2017 user.notice root: guidebug dnsmasq reload
	Wed Mar 22 18:26:06 2017 user.notice root: guidebug dnsmasq startsrv ,
	Wed Mar 22 18:26:06 2017 user.notice root: guidebug dnsmasq realstart cfg02411c wait 20
	Wed Mar 22 18:26:08 2017 user.notice root: guidebug dnsmasq realstart cfg02411c wait 18

This one I also have no clue about.  It didn't even make it to the "realstart"
part.  So checking further what happened in between was causing that should be
helpful

	Wed Mar 22 18:26:10 2017 user.notice root: guidebug dnsmasq init
	Wed Mar 22 18:26:10 2017 user.notice root: guidebug dnsmasq reload
	Wed Mar 22 18:26:10 2017 user.notice root: guidebug dnsmasq startsrv ,