From c21582bc901bd7a8ee8ec19812b737e9b3c6f042 Mon Sep 17 00:00:00 2001 From: Pieter Lexis Date: Sun, 4 Jan 2015 14:55:16 +0100 Subject: [PATCH] Expand a little on the virtual hosting docs Closes #494 in the process --- docs/markdown/authoritative/settings.md | 8 ++++++-- docs/markdown/authoritative/virtual.md | 24 ++++++++++++++++++++---- 2 files changed, 26 insertions(+), 6 deletions(-) diff --git a/docs/markdown/authoritative/settings.md b/docs/markdown/authoritative/settings.md index b686982552..79cf458fb8 100644 --- a/docs/markdown/authoritative/settings.md +++ b/docs/markdown/authoritative/settings.md @@ -90,7 +90,6 @@ Location of configuration directory (`pdns.conf`). Usually `/etc/powerdns`, but this depends on `SYSCONFDIR` during compile-time. ## `config-name` - * String Name of this virtual configuration - will rename the binary image. See ["Virtual hosting"](virtual.md). @@ -641,7 +640,12 @@ under that offset. * Path Where the controlsocket will live. The default depends on `LOCALSTATEDIR` during -compile-time. See ["Controlsocket"](internals.md#controlsocket). +compile-time (usually `/var/run` or `/run`). See +["Controlsocket"](internals.md#controlsocket). + +This path will also contain the pidfile for this instance of PowerDNS called +`pdns.pid` by default. See [`config-name`](#config-name) and +[Virtual Hosting](virtual.md) how this can differ. ## `strict-rfc-axfrs` * Boolean diff --git a/docs/markdown/authoritative/virtual.md b/docs/markdown/authoritative/virtual.md index 2b117a32f7..422190b82a 100644 --- a/docs/markdown/authoritative/virtual.md +++ b/docs/markdown/authoritative/virtual.md @@ -1,8 +1,24 @@ # Virtual Hosting -It may be advantageous to run multiple separate PDNS installations on a single host, for example to make sure that different customers cannot affect each others zones. PDNS fully supports running multiple instances on one host. +It may be advantageous to run multiple separate PowerDNS installations on a +single host, for example to make sure that different customers cannot affect +each others zones. PowerDNS fully supports running multiple instances on one host. -To generate additional PDNS instances, copy the init.d script `pdns` to `pdns-name`, where `name` is the name of your virtual configuration. Must not contain a - as this will confuse the script. +To generate additional PowerDNS instances, copy the init.d script `pdns` to +`pdns-name`, where `name` is the name of your virtual configuration. Must not +contain a - as this will confuse the script. -When you launch PDNS via this renamed script, it will seek configuration instructions not in `pdns.conf` but in `pdns-name.conf`, allowing for separate specification of parameters. +When you launch PowerDNS via this renamed script, it will seek configuration +instructions not in `pdns.conf` but in `pdns-name.conf`, allowing for separate +specification of parameters. -**Warning**: Be aware however that the init.d `force-stop` will kill all PDNS instances! +Internally, the init script calls the binary with the +[`config-name`](settings.md#config-name) option set to `name`, setting in motion +the loading of separate configuration files. + +When you launch a virtual instance of PowerDNS, the pid-file is saved inside +[`socket-dir`](settings.md#socket-dir) as `pdns-name.pid`. + +**Warning**: Be aware however that the init.d `force-stop` will kill all +PowerDNS instances! + +**Warning**: For systems running systemd, virtual hosting is not yet supported. -- 2.47.2