Thanks Simon, I did everything again, but now running sudo systemctl edit nsd and saving [Service] ReadWritePaths=/var/log/nsd Then I have run sudo systemctl daemon-reload sudo systemctl restart nsd Since the change was not reflected in /lib/systemd/system/nsd.service, I restarted the system, but the change is still not reflected in /lib/systemd/system/nsd.service and the log is not written. What other change should I make ?. Best regards. Jos? Luis El jue, 24-10-2019 a las 09:52 -0400, Simon Deziel escribi?:> On 2019-10-24 9:29 a.m., Jos? Luis Artuch wrote: > > cp /lib/systemd/system/nsd.service{,_original} > > nano /lib/systemd/system/nsd.service > > If/when nsd's package is updated, your custom edits will be lost. > That's > why I suggested the "systemctl edit" way to just add a local > override/drop-in file that would survive package updates. > > Regards, > Simon > _______________________________________________ > nsd-users mailing list > nsd-users at NLnetLabs.nl > https://open.nlnetlabs.nl/mailman/listinfo/nsd-users
Hi Jos?, On Thu, 2019-10-24 at 15:18 -0300, Jos? Luis Artuch wrote:> Thanks Simon, > > I did everything again, but now running > sudo systemctl edit nsd > and saving > [Service] > ReadWritePaths=/var/log/nsd > > Then I have run > sudo systemctl daemon-reload > sudo systemctl restart nsd > > Since the change was not reflected in > /lib/systemd/system/nsd.service, > I restarted the system, but the change is still not reflected in > /lib/systemd/system/nsd.service and the log is not written. > What other change should I make ?The changes will not be reflected in /lib/systemd/system/nsd.service, instead a new file will be written in /etc/systemd/system/nsd.service which should reflect your changes(?). This is done so that changes are kept through upgrades, which is the point that both Simon and Vladimir are making. Hope that helps.> Best regards. > Jos? Luis > > El jue, 24-10-2019 a las 09:52 -0400, Simon Deziel escribi?: > > On 2019-10-24 9:29 a.m., Jos? Luis Artuch wrote: > > > cp /lib/systemd/system/nsd.service{,_original} > > > nano /lib/systemd/system/nsd.service > > > > If/when nsd's package is updated, your custom edits will be lost. > > That's > > why I suggested the "systemctl edit" way to just add a local > > override/drop-in file that would survive package updates. > > > > Regards, > > Simon > > _______________________________________________ > > nsd-users mailing list > > nsd-users at NLnetLabs.nl > > https://open.nlnetlabs.nl/mailman/listinfo/nsd-users > > _______________________________________________ > nsd-users mailing list > nsd-users at NLnetLabs.nl > https://open.nlnetlabs.nl/mailman/listinfo/nsd-users- Jeroen
On 2019-10-24 2:18 p.m., Jos? Luis Artuch wrote:> Thanks Simon, > > I did everything again, but now running > sudo systemctl edit nsd > and saving > [Service] > ReadWritePaths=/var/log/nsd > > Then I have run > sudo systemctl daemon-reloadReloading is not needed as "edit" takes care of this once you save.> sudo systemctl restart nsd > > Since the change was not reflected in /lib/systemd/system/nsd.service,That is correct. The drop-in files are stored in /etc/systemd/system/nsd.service.d/*.conf (override.conf by default). "systemctl cat nsd" will list the various files it aggregates to form the resulting unit definition.> I restarted the system, but the change is still not reflected in > /lib/systemd/system/nsd.service and the log is not written. > What other change should I make ?.In theory nothing else is needed. Do you still get the error about read-only FS? If yes, make sure your nsd.conf points to a file under the directory /var/log/nsd. Simon