Fix #159: hacky generation of /etc/resolv.conf at boot

To be able to run "resolvconf -u" at boot we need dnsmasq up and running and startup-config having been loaded successfully. (No point when we hare in fail secure mode.) If this bugs out it can be pinpointed by an empty /etc/resolv.conf Signed-off-by: Joachim Wiberg <[email protected]>
kernelkit · Oct 17, 2023 · aa655ab · aa655ab
1 parent cefe24c
commit aa655ab
Showing 1 changed file with 3 additions and 2 deletions.
diff --git a/package/confd/confd.conf b/package/confd/confd.conf
@@ -27,5 +27,6 @@ service name:netopeer log \
 	[12345789] <pid/confd> netopeer2-server -F -t 60 \
 	-- NETCONF server
 
-# XXX: This is a hack, talk to Joachim
-task [12345789] resolvconf -u -- Update DNS configuration
+# Create initial /etc/resolv.conf after successful bootstrap
+task name:resolv :conf norestart if:<run/startup/success> \
+	[S] <pid/dnsmasq> resolvconf -u -- Update DNS configuration