On Thu, Sep 28, 2023 at 14:30 IHI IHI via Pdns-users <
pdns-users@mailman.powerdns.com> wrote:
> Hello
> When upgrading to a new version(PowerDNS Recursor v4.7-->4.8-->4.9-->5),
> despite choosing to keep the current configuration file,but its tuning
> parameters at
> pdns-recursor.service(/lib/sy
Hi,
That is because the files inside of /lib/systemd/system/ should not
be changed directly (for the dpkg package management, it is not a
configuration file per si) and like Kebin mentioned before, you need
to override the parameters that you want using "systemctl edit pdns",
which will create a
If you are editing the service unit file, don't. Use the systemd override
mechanism to apply your changes so they won't be override.
On Thu, Sep 28, 2023, at 16:30, IHI IHI via Pdns-users wrote:
> Hello
> When upgrading to a new version(PowerDNS Recursor v4.7-->4.8-->4.9-->5),
> despite choosing
Hi
How are you making the upgrades ??
Salu2
On Thu, Sep 28, 2023, 22:30 IHI IHI via Pdns-users <
pdns-users@mailman.powerdns.com> wrote:
> Hello
> When upgrading to a new version(PowerDNS Recursor v4.7-->4.8-->4.9-->5),
> despite choosing to keep the current configuration file,but its tuning
>
Hello
When upgrading to a new version(PowerDNS Recursor v4.7-->4.8-->4.9-->5),
despite choosing to keep the current configuration file,but its tuning
parameters at
pdns-recursor.service(/lib/systemd/system/pdns-recursor.service) will
return to its default values!
for example:
# my Tuning
LimitNOFIL
