20.04.2022 23:56, Petr Cech wrote:
Package: unbound
Version: 1.15.0-4
Severity: normal
Hi,
I have unbound installed but masked in systemd. So when postinst of
unbound runs unbound-resolvconf.service I end up with "broken"
resolv.conf pointing to localhost but with no running resolver.
I'm not sure, if the fix should be in unbound-resolvconf.service
file or the postinst should check if unbound is enabled.
Hello Petr! Thank you for the bug report!
Can you say if it worked correctly before? I don't know how unbound-resolvconf
is supposed to work to start with, I'm new with unbound package and haven't yet
managed to look at the resolvconf service at all.
To me if the thing is tied to unbound, maybe unbound-resolvconf should depend
on unbound somehow. Or maybe, if you disable unbound, you should disable (mask)
unbound-resolvconf *too* (just don't know about it).
I'll take a look, - as I said, for now I don't even know what's the purpose of
this additional service. When I first come across it, it looked somewhat
unusual.
(The thing is installed the usual way, using dh_installsystemd, so postinst
fragment is generated automatically)
But overall, what's the purpose of installing unbound if it is not used as a
service? I'm curious as of how people use software whey install.
(FWIW, for some years I used my own version of unbound.service which worked
correctly with chroot, - something which has been broken for quite some time
and is hopefully fixed in 1.15).
Thanks,
/mjt
