On Thu, 29 Oct 2020 16:53:43 +0000
g4sra via Dng <dng@???> wrote:

> On 29/10/2020 13:44, Michael Neuffer wrote:
> > On 10/29/20 2:27 PM, dng@??? wrote:
> --snip--
> >> To ease the maintenance of those servers i intend to migrate them
> >> to docker containers. I wonder people on this list have experience
> >> on this subject?
> >
> >
> > You might want to take a look at this project:
> >
> > https://github.com/mailserver2/mailserver
>
> Please correct me if I am mistaken, I thought 'unbound' was tied to
> 'systemd creep' nowadays and have been avoiding it for that reason
> alone. I want to avoid creating a dependency on something I don't
> already have only to need to purge it next year ...

I'm as anti-systemd as the next guy, but I use unbound on a constant,
everyday basis. Let me explain...

Here are two lines from my unbound.conf:

======================================================
# Guard against future default changes: no systemd ever!
use-systemd: no
======================================================

As far as I can see, if I had set use-systemd to "yes", unbound would
have reported its success in starting in the systemd approved way, and
would not have backgrounded itself. So if you use sysvinit, you just
say use-systemd: no and whatever option that makes it background
itself. If you use runit or s6, say systemd: no and whatever makes it
NOT background itself.

So basically, there's a little, probably completely separate part of
unbound with minimal linkage, that if told to, will send out a
systemd-approved "I am functional now" message. But as far as I know,
unbound uses no systemd facilities and would only require or suggest
systemd as a result of a systemd-infected distro configuring unbound
that way.

I have a lot of confidence in unbound.

SteveT

Steve Litt
Autumn 2020 featured book: Thriving in Tough Times
http://www.troubleshooters.com/thrive