<div style="font-family: Arial; text-align: left; font-size: 14px; color: #000000;">> [...] I'd double check if it's indeed effective with "systemctl show nsd | grep ReadWritePaths"</div><div style="font-family: Arial; text-align: left; font-size: 14px; color: #000000;"><br>Seems to be effective:</div><div style="font-family: Arial; text-align: left; font-size: 14px; color: #000000;">> # systemctl show nsd | grep ReadWritePaths</div><div style="text-align: left;"><span style="font-size: 14px;">> ReadWritePaths=/var/lib/nsd /var/log /etc/nsd /run</span></div><div style="text-align: left;"><span style="font-size: 14px;"><br></span></div><div style="text-align: left;"><span style="font-size: 14px;">The problem with the log file will never stop the NSD service from working (I believe) but the log file is quite important, so, of course, NSD should be able to append to it.</span></div><div style="text-align: left;"><span style="font-size: 14px;"><br></span></div><div style="text-align: left;"><span style="font-size: 14px;">Does anyone already had this problem after an upgrade?</span></div><div style="text-align: left;"><span style="font-size: 14px;"><br></span></div><div style="text-align: left;"><span style="font-size: 14px;">Kind Regards,</span></div><div style="text-align: left;"><span style="font-size: 14px;">Kaulkwappe</span></div><div style="text-align: left;"><span style="font-size: 14px;"><br></span><br><hr style="color: rgb(0, 0, 0); font-family: Arial; font-size: 14px; border-width: 0px 0px 1px; border-top-style: initial; border-right-style: initial; border-left-style: initial; border-top-color: initial; border-right-color: initial; border-left-color: initial; border-image: initial; border-bottom-style: solid; border-bottom-color: rgb(218, 218, 218);"><b style="color: rgb(0, 0, 0); font-family: Arial; font-size: 14px;">From:</b><span style="font-size: 14px;"> Simon Deziel <</span><a href="/email/new/1/simon%40sdeziel.info" style="color: rgb(0, 0, 0); font-family: Arial; font-size: 14px;">simon@sdeziel.info</a><span style="font-size: 14px;">></span><br><b style="color: rgb(0, 0, 0); font-family: Arial; font-size: 14px;">Sent:</b><span style="font-size: 14px;"> Monday, 25. Nov 2019 – 01:26 CET +0100</span><br><b style="color: rgb(0, 0, 0); font-family: Arial; font-size: 14px;">To:</b> <a href="/email/new/1/nsd-users%40NLnetLabs.nl" style="color: rgb(0, 0, 0); font-family: Arial; font-size: 14px;">nsd-users@NLnetLabs.nl</a><br><br><b style="color: rgb(0, 0, 0); font-family: Arial; font-size: 14px;">Subject:</b><span style="font-size: 14px;"> Re: [nsd-users] Permission error after upgrade to Debian Buster (10.2)</span><br><br></div><div>
<style>
body {
font-family: "Arial";
font-size: 100% !important;
margin: 0;
line-height: 1.2rem;
}
</style>
<pre style="white-space: pre-wrap; color: #173860;">On 2019-11-24 6:10 p.m., Kaulkwappe wrote:
> Hi Simon,
>
> > I would have expect a permission error instead of a "read-only" one. It
> > looks as if /var/log was not properly added to be ReadWritePaths set.
>
> That is what I have used:
> > ReadWritePaths=/var/lib/nsd /var/log /etc/nsd /run
Not sure what would explain the read-only error then. I'd double check
if it's indeed effective with "systemctl show nsd | grep ReadWritePaths"
> > This unlink failure is expected and AFAICT harmless.
> It should be harmless, but it doesn't look nice. I would consider this as a bug.
Agreed. Interestingly, unbound accepts "-p" to skip managing its own
PID. If nsd could get this, it would be handy when managing the daemon
with systemd.
> > I believe that xfrd.state should be owned by nsd:nsd as the daemon needs
> > to write to that file.
> After changing the owner to nsd:nsd I believe this problem is fixed. Thanks!
Glad to hear that!
Regards,
Simon
_______________________________________________
nsd-users mailing list
nsd-users@NLnetLabs.nl
https://open.nlnetlabs.nl/mailman/listinfo/nsd-users
</pre>
</div>