On 2023-01-18 13:39, Jeffrey Walton wrote:
On Wed, Jan 18, 2023 at 6:25 AM Jesper Dybdal wrote:
That leaves one file in the system with the name "bind9.service":
/var/lib/systemd/deb-systemd-helper-enabled/multi-user.target.wants/bind9.service
Can I safely delete that one (I suspect so)? Will
On 2023-01-18 13:55, Greg Wooledge wrote:
On Wed, Jan 18, 2023 at 12:25:03PM +0100, Jesper Dybdal wrote:
That leaves one file in the system with the name "bind9.service":
/var/lib/systemd/deb-systemd-helper-enabled/multi-user.target.wants/bind9.service
Can I safely delete that one (I suspect
On Wed, Jan 18, 2023 at 12:25:03PM +0100, Jesper Dybdal wrote:
> I have now, in order:
> * Disabled bind9.service
> * Corrected /etc/default/named so the named service can start (it was
> missing the chroot)
> * Stopped bind9.service
> * Started named.service and checked that named i actually
On Wed, Jan 18, 2023 at 6:25 AM Jesper Dybdal wrote:
>
>
> On 2023-01-16 13:36, Greg Wooledge wrote:
> > On Mon, Jan 16, 2023 at 10:42:35AM +0100, Jesper Dybdal wrote:
> >> 28969163 4 -rw-r--r-- 1 root root 255 Jun 2 2016
> >> /etc/systemd/system/bind9.service
> >>
> >> I
On 2023-01-16 13:36, Greg Wooledge wrote:
On Mon, Jan 16, 2023 at 10:42:35AM +0100, Jesper Dybdal wrote:
28969163 4 -rw-r--r-- 1 root root 255 Jun 2 2016
/etc/systemd/system/bind9.service
I suspect that the bind9 service ought to be removed. Is that correct?
...
In
On Mon, Jan 16, 2023 at 03:51:52PM +0100, Jesper Dybdal wrote:
> I'll do that. Should I then also remove the "Alias=bind9.service" line from
> named.service?
If Debian put it there, then no. Leave it alone. It's probably just
a backward compatibility shim, from when the service name used to be
On 2023-01-16 13:36, Greg Wooledge wrote:
On Mon, Jan 16, 2023 at 10:42:35AM +0100, Jesper Dybdal wrote:
28969163 4 -rw-r--r-- 1 root root 255 Jun 2 2016
/etc/systemd/system/bind9.service
I suspect that the bind9 service ought to be removed. Is that correct?
It looks
On Mon, Jan 16, 2023 at 10:42:35AM +0100, Jesper Dybdal wrote:
> 28969163 4 -rw-r--r-- 1 root root 255 Jun 2 2016
> /etc/systemd/system/bind9.service
>
> I suspect that the bind9 service ought to be removed. Is that correct?
It looks like you (or someone acting on your
I'm running Buster. I then had a problem with BIND and DNSSEC, so I
upgraded my bind9 package to the one in buster-backports.
But it seems that this has involved a partial rename of the systemd unit
from bind9 to named. So I now have two almost equal systemd units. And
named.service
9 matches
Mail list logo
