On Thu, Jun 15, 2023 at 09:02:05AM +, Giddings, Bret wrote:
> I can confirm that one solution is
>
> umask 0022
> mkdir /var/cache/bind/run/systemd
> touch /var/cache/bind/run/systemd/notify
> mount --bind /run/systemd/notify /var/cache/bind/run/systemd/notify
>
> I had previously tried
as it is by
no means obvious that this has changed and how to resolve it.
Many thanks,
Regards,
-Original Message-
From: Marc Haber
Sent: 15 June 2023 06:09
To: Ondřej Surý ; 1037...@bugs.debian.org
Cc: Giddings, Bret
Subject: Re: Bug#1037966: bind9: Unable to restart bind9 via
On Thu, Jun 15, 2023 at 06:36:10AM +0200, Ondřej Surý wrote:
> Your chroot is missing the sd_notify socket. The package can’t really expect
> all non-default configurations. I can probably add a NEWS.Debian entry for
> this, but it’s certainly not important severity.
Maybe it would also be a
Control: severity -1 minor
Your chroot is missing the sd_notify socket. The package can’t really expect
all non-default configurations. I can probably add a NEWS.Debian entry for
this, but it’s certainly not important severity.
Ondrej
--
Ondřej Surý (He/Him)
> On 14. 6. 2023, at 23:15, Bret
Package: bind9
Version: 1:9.18.12-1
Severity: important
Dear Maintainer,
Whilst attempting to upgrade from debian 11 to 12, for my chroot named setup, I
found that running
systemctl restart named
would hang and eventually timeout. It should be noted that named is running
fine.
Having
5 matches
Mail list logo
