Joachim Wiberg 3e07c9a960 Fix missing /etc/resolv.conf when starting with failure-config ...

Turns out the root cause for the odd log message in #896 was that the
system did not properly call `resolvconf -u` when starting in failure
mode.

This patch simplifies the code by moving all `resolvconf -u` calls to
the same Finit task.  Ensuring it is first launched when confd has
successfully consumed any configuration at boot, and then every time
a static DNS server is added.  (The udhcpc client script already call
`resolvconf -u` when dynamic DNS servers are learned.)

Fixes #896

Signed-off-by: Joachim Wiberg <troglobit@gmail.com>

2025-02-28 16:10:27 +01:00

..

avahi.service

package/confd: install avahi _netconf-ssh._tcp service record

2023-11-29 07:34:05 +01:00

confd.conf

Fix missing /etc/resolv.conf when starting with failure-config

2025-02-28 16:10:27 +01:00

confd.hash

package/confd: add LICENSE hash

2024-04-11 06:19:07 +02:00

confd.mk

Fix missing /etc/resolv.conf when starting with failure-config

2025-02-28 16:10:27 +01:00

Config.in

package/confd: drop empty help text

2024-06-28 12:54:27 +02:00

resolvconf.conf

Fix missing /etc/resolv.conf when starting with failure-config

2025-02-28 16:10:27 +01:00

tmpfiles.conf

confd: generate test-config.cfg

2024-08-23 11:15:12 +02:00