thelonelycoder
Part of the Furniture
I have a peculiar problem which I can reproduce on 384.17.
When Changing a state through the Diversion WebUI, the following relevant events are logged in syslog:
The httpd requests service restart_diversion which runs a Diversion file that sets the new state of services, then issues a restart of Dnsmasq.
But that request is skipped over and consequently leaves Diversion in a state where the service is disabled in its settings, but the changes are not written to dnsmasq.conf.
Is there any way I can force a service restart_dnsmasq?
I have lowered the httpd wait time to 4 and 1 secs in the page: <input type="hidden" name="action_wait" value="4">
Still no luck.
@RMerlin ?
When Changing a state through the Diversion WebUI, the following relevant events are logged in syslog:
Code:
rc_service: httpd 6400:notify_rc restart_diversion
custom_script: Running /jffs/scripts/service-event (args: restart diversion)
Diversion: WebUI action, ad-blocking state changed to off
rc_service: service 21086:notify_rc restart_dnsmasq
rc_service: waitting "restart_diversion" via httpd ...
rc_service: skip the event: restart_dnsmasq.
The httpd requests service restart_diversion which runs a Diversion file that sets the new state of services, then issues a restart of Dnsmasq.
But that request is skipped over and consequently leaves Diversion in a state where the service is disabled in its settings, but the changes are not written to dnsmasq.conf.
Is there any way I can force a service restart_dnsmasq?
I have lowered the httpd wait time to 4 and 1 secs in the page: <input type="hidden" name="action_wait" value="4">
Still no luck.
@RMerlin ?