your changelog snippet is handeled as signature seperator so a forward when someone starts complaining "Since years, Debian and Ubuntu User, and plenty of scripts and automation software (Puppet ...), know that the service is called" i assume that he at least would have tried if something is broken *before* complain and so it's a logicla assumption the alias is missing
Debian/Ubuntu packages and what should be done there before the next major release of the distribution don't belong here anyways -------- Weitergeleitete Nachricht -------- Betreff: Re: Debian/Ubuntu: Why was the service renamed from bind9 to named? Datum: Wed, 15 Apr 2020 10:04:39 +0200 Von: Ondřej Surý <ond...@isc.org> > On 15 Apr 2020, at 09:05, Reindl Harald <h.rei...@thelounge.net> wrote: > > BTW in case Debian/Ubuntu when they do RTFM it wouldn't be an issue at all Is this the case of you being rude instead of getting the facts? bind9 (1:9.15.3-2) unstable; urgency=medium * Fix the section for bind9 alias in the systemd unit [GL #1193] $ cat named.service [Unit] Description=BIND Domain Name Server Documentation=man:named(8) After=network.target Wants=nss-lookup.target Before=nss-lookup.target [Service] EnvironmentFile=-/etc/default/named ExecStart=/usr/sbin/named -f $OPTIONS ExecReload=/usr/sbin/rndc reload ExecStop=/usr/sbin/rndc stop [Install] WantedBy=multi-user.target Alias=bind9.service _______________________________________________ Please visit https://lists.isc.org/mailman/listinfo/bind-users to unsubscribe from this list bind-users mailing list bind-users@lists.isc.org https://lists.isc.org/mailman/listinfo/bind-users
