aboutsummaryrefslogtreecommitdiffstats
path: root/target/sdk/files
diff options
context:
space:
mode:
authorJo-Philipp Wich <jo@mein.io>2018-07-17 07:47:33 +0200
committerJo-Philipp Wich <jo@mein.io>2018-07-17 08:10:20 +0200
commit1bad852ff597fd0535e02703f0c4b83447aaff45 (patch)
tree85fcc5b69e0732c74508432e783bf2ad6371d6c7 /target/sdk/files
parent18b87b10a99bc445b3beae737ddce38d228c5d24 (diff)
downloadupstream-1bad852ff597fd0535e02703f0c4b83447aaff45.tar.gz
upstream-1bad852ff597fd0535e02703f0c4b83447aaff45.tar.bz2
upstream-1bad852ff597fd0535e02703f0c4b83447aaff45.zip
base-files: network.sh: gracefully handle missing network.interface ubus ns
When attempting to use any of the functions in network.sh while netifd is not started yet, the ubus interface dump query will fail with "Not found", yielding an empty response. Subsequently, jsonfilter is invoked with an empty string instead of a valid JSON document, causing it to emit a second "unexpected end of data" error. This caused the dnsmasq init script to log the following errors during early boot on some systems: procd: /etc/rc.d/S19dnsmasq: Command failed: Not found. procd: /etc/rc.d/S19dnsmasq: Failed to parse json data: unexpected end of data. Fix the issue by allowing the ubus query to fail with "Not found" but still logging other failures, and by passing an empty JSON object to jsonfilter if the interface status cache is empty. Signed-off-by: Jo-Philipp Wich <jo@mein.io>
Diffstat (limited to 'target/sdk/files')
0 files changed, 0 insertions, 0 deletions