> Can you show me where PowerDNS store Query cache and Packet cache ? If it's
> in HDD, can we move it to RAM ? And finally, does it have any limit (size,
> ttl, .) ? I'am using PowerDNS 3.X.X. Please help me!
It's stored in RAM, and is limited by your available memory. There
are suggested sizes i
Dear All,
Can you show me where PowerDNS store Query cache and Packet cache ? If it's
in HDD, can we move it to RAM ? And finally, does it have any limit (size,
ttl, .) ? I'am using PowerDNS 3.X.X. Please help me!
Thanks & Best Regards,
--
Hello Volker,
On 1 Aug 2016, at 22:24, Volker Janzen wrote:
Is the kernel version a strict requirement for PowerDNS? E.g.
Virtuozzo 6 will have many years of support left, Debian Jessie is
known to run well in Virtuozzo 6 containers. I think 50% of my cluster
runs a 2.6.32 kernel that still r
Hi Remi,
I can now say why it works with the 2.6.32x RHEL kernel, they backported the
required feature: https://rhn.redhat.com/errata/RHSA-2015-0864.html
So systemd only has issues when not using the RHEL version of 2.6.32x kernel or
using kernel < 3.5.
Finally I can say it's fine to run Power
Hi Remi,
> Sorry if I have been unclear about that yesterday, when I wrote "I'm
> pretty sure you are going to have other issues if you run Jessie on top
> of an older kernel than the one shipped with Jessie" I wasn't referring
> to issues with PowerDNS. But I have been bitten by this kind of setu
On 02/08/2016 17:35, Peter Thomassen wrote:
pdns 4.0.0~alpha2 version
that comes with Ubuntu 16.04
Don't use this version - it's got some serious mysql problems.
https://mailman.powerdns.com/pipermail/pdns-users/2016-March/024085.html
https://mailman.powerdns.com/pipermail/pdns-users/2016-May/
Hi,
I recently run pdnsutil rectify-zone, with the pdns 4.0.0~alpha2 version
that comes with Ubuntu 16.04. I am using the MySQL background, and got a
deadlock:
Error:
GSQLBackend unable to update ordername and auth for domain_id 3390:
Could not execute mysql statement: update records set ordernam
On 02/08/2016 15:52, Volker Janzen wrote:
they just say it's strongly recommended. It's not mandatory and BTW
would not make sense when it's a container running under host system
kernel (e.g. 2.6.x). You might brake your container when installing
this kernel package.
I only pointed this out b
Hi,
they just say it's strongly recommended. It's not mandatory and BTW would not
make sense when it's a container running under host system kernel (e.g. 2.6.x).
You might brake your container when installing this kernel package.
Regards
Volker
Am 02.08.2016 um 16:20 schrieb Brian Candle
On 02/08/2016 14:39, Remi Gacogne wrote:
>This was a manual step and not part of the dist-upgrade process.
I'm a bit surprised about that, but OK.
You need to install a metapackage to get the kernel upgraded: see
https://www.debian.org/releases/stable/i386/release-notes/ch-upgrading.en.html#ne
Hi Volker,
On 08/02/2016 03:32 PM, Volker Janzen wrote:
> I'm able to confirm that the unmodified systemd configuration works
> when I update to the kernel regular shipped with Debian Jessie.
Thank you for confirming this!
> This was a manual step and not part of the dist-upgrade process.
I'm a
Hi Remi,
> Am 01.08.2016 um 18:52 schrieb Remi Gacogne :
>
> Well, you'll have to check what the Debian policy is, but I'm pretty
> sure you are going to have other issues if you run Jessie on top of an
> older kernel than the one shipped with Jessie.
I'm able to confirm that the unmodified syst
12 matches
Mail list logo
