On Thu, Jun 15, 2023 at 09:02:05AM +0000, 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 this, but my default system umask for root is 0077 and > I therefore initially created the directory with more restrictive permissions > that meant that it still didn't work. Once I had correct that, it did indeed > work. > > I'll review the unbound patch and see if I can put it all in systemd using > ExecStartPre. > > If something could be documented, that would be incredibly helpful as it is > by no means obvious that this has changed and how to resolve it.
Maybe this could even be solved implicitly by having a template unit that takes the path to the chroot as instance name and then automatically does all the right motions to set up the chroot etc. In any case, neighter the improved docs nor the template unit is likely to show up in Debian bookworm. Greetings Marc -- ----------------------------------------------------------------------------- Marc Haber | "I don't trust Computers. They | Mailadresse im Header Leimen, Germany | lose things." Winona Ryder | Fon: *49 6224 1600402 Nordisch by Nature | How to make an American Quilt | Fax: *49 6224 1600421
