On Wed, Jan 18, 2023 at 6:25 AM Jesper Dybdal <jd-debian-u...@dybdal.dk> 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 suspect that the bind9 service ought to be removed. Is that correct?
> > ...
> > In any case, yeah, I'd get rid of that. Maybe move it to /root/ in case
> > you want to refer to it in the future, or whatever. Afterward, do a
> > "systemctl daemon-reload".
> >
> 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 running
> * Deleted /etc/systemd/system/bind9.service
> * Deleted /etc/default/bind9
> * Run systemctl daemon-reload
> * Checked that "systemctl restart named.service" works
>
> 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 it be a problem
> during reboot if I leave it?
if you are manually deleting the bind9 gear, you may as well go full
in. You can't get half pregnant.
Find the bind9 artifacts left on the system:
find /etc -name 'bind9*'
Then whack it:
find /etc -name 'bind9*' -exec rm -f {} \;
Jeff
