Michael Biebl wrote: > Ok, I guess I have the missing ingredient now. We need to make the > unbound-resolvconf.service unit use Type=simple not oneshot. > oneshot blocks until the started process has completed, with Type=simple > we don't block.
Hi, Michael: I tested this (actually your later version with the typo fix), but it seems unbound-resolvconf.service starts, but then immediately stops: ● unbound-resolvconf.service - Unbound DNS server via resolvconf Loaded: loaded (/lib/systemd/system/unbound-resolvconf.service; enabled; vendor preset: enabled) Active: inactive (dead) since Mon 2016-07-04 23:27:10 UTC; 10s ago Process: 1416 ExecStop=/usr/lib/unbound/package-helper resolvconf_stop (code=exited, status=0/SUCCESS) Process: 1387 ExecStart=/usr/lib/unbound/package-helper resolvconf_start (code=exited, status=0/SUCCESS) Main PID: 1387 (code=exited, status=0/SUCCESS) Jul 04 23:27:10 debian systemd[1]: Started Unbound DNS server via resolvconf. Jul 04 23:27:10 debian package-helper[1387]: executing resolvconf_start Jul 04 23:27:10 debian package-helper[1416]: executing resolvconf_stop (I inserted an echo at the top of the package-helper script just to verify.) This is not what we need, because the local Unbound gets added to /etc/resolv.conf (when ExecStart runs) and then immediately removed a split second later (when ExecStop runs). Do we need to set “RemainAfterExit=yes” in unbound-resolvconf.service? Thanks! -- Robert Edmonds edmo...@debian.org
