1. 12 Mar, 2019 3 commits
  2. 14 Aug, 2018 1 commit
    • Petr Špaček's avatar
      rebrand to "Knot Resolver" · 42123aad
      Petr Špaček authored
      Previously we were using names "Knot DNS Resolver" and "Knot Resolver"
      interchangibly and the prefix "Knot DNS" was somehow confusing users.
      Let's see if this rebranding actually helps or not.
  3. 02 Jul, 2018 2 commits
  4. 16 Feb, 2018 4 commits
    • Tomas Krizek's avatar
    • Tomas Krizek's avatar
      systemd: provide kresd arguments in ExecStart= · 24711da7
      Tomas Krizek authored
      To avoid using /etc/default/kresd, provide the needed arguments directly
      in the ExecStart= in the kresd@.service.
    • Tomas Krizek's avatar
      systemd: remove kresd.service meta-service · 1f9aa9a6
      Tomas Krizek authored
      The kresd.service meta-service could be confusing for users and provides
      no extra functionality. The system-kresd.slice can be used to restart or
      stop all running instances.
      Distributions shipping with /etc/init.d/kresd should symlink the
      kresd.service to /dev/null to prevent systemd-sysv-generator from
      creating this service.
    • Daniel Kahn Gillmor's avatar
      More systemd service management cleanup · 0398a985
      Daniel Kahn Gillmor authored
      Please see discussion at:
      The new approach is:
       * non-templated kresd.socket and kresd-tls.socket, for the
         public-facing listening ports.  They know to invoke kresd@1.service
         if they're socket-activated.
       * kresd@.service *is* templated, to allow the admin to add more
         concurrent runners with:
            systemctl enable kresd@2.service
       * kresd-control@.socket is still templated, since each daemon has a
         separately-addressable different control port.
       * non-templated kresd.service is a dummy meta-service.  it is in the
         same slice as kresd@.service, and all the kresd@.service instances
         are PartOf= it, so you should be able to stop and restart all
         services together.  On systems like debian that ship
         /etc/init.d/kres, this also avoids having systemd-sysv-generator
         create a kresd.service based on the initscript.
       * no templated instances are explicitly instantiated during initial
         ship, but kresd@1.service should be socket-activated cleanly
      Gbp-Pq: Name 0010-More-systemd-service-management-cleanup.patch
  5. 30 Jan, 2018 1 commit
    • Tomas Krizek's avatar
      systemd: enable multiple processes with socket activation · 4905226d
      Tomas Krizek authored
      In order to be able to spawn multiple processes with socket activation,
      systemd template (see systemd.unit(5)) is used. This allows the user to
      create any amount of instances by simply providing a unique name for
      each of them. The most sensible instance identifiers are natural
      numbers, but any convention could be used.
      The default recommended service name becomes kresd@1.service, replacing
      the older kresd.service. Sockets are renamed in a similar way. Users are
      able to take advantage of bash expansion to spawn/control multiple
      processes, e.g. "systemctl start kresd@{1..16}.service"
      The socket-activated service can now be launched directly with
      "systemctl start kresd@1.service", which will request the associated
      sockets without the need for any extra priviledges or capabilities.
      Stopping the kresd service now also stops the associated sockets.
      Stopping any individual socket is an isolated opration now (stopping
      kresd@1.socket no longer stop kresd-tls@1.socket and
      Users and packagers are also encouraged to use drop-in files for extra
      configuration or modifications to ensure compatibility with their
  6. 11 Jan, 2018 2 commits
    • Tomas Krizek's avatar
      systemd: add knot-resolver alias · 921feae2
      Tomas Krizek authored
      The `knot-resolver` name is used for paths and user name. Creating a
      systemd alias with the same name is user-friendly to end users who won't
      have to remember another name (`kresd`).
      Note: Systemd Alias is only created after service is enabled. Packagers
      are thus advised to create symlinks for unit files during package installation
      so users can use `knot-resolver` name right from the start.
    • Tomas Krizek's avatar
      systemd: use persistent cache by default · 8ffb00f8
      Tomas Krizek authored
      The /run directory is non-persistent. Use /var/cache/knot-resolver
      as a persistent cache.
  7. 10 Jan, 2018 2 commits
  8. 19 Oct, 2017 1 commit
    • Daniel Kahn Gillmor's avatar
      systemd: drop RefuseManualStart=true, disable kresd.service by default · a0d93df6
      Daniel Kahn Gillmor authored
      I introduced RefuseManualStart=true last year when writing the initial
      systemd unit file for kresd.  I did this because i didn't want to
      start running the daemon if no one was going to talk to it.
      I'm no longer convinced that this directive has a good justification.
      While i think that there is no need to activate the service without
      socket activation, i think preventing manual invocation is actively
      harmful (admins will reflexively do "systemctl restart kresd" just
      like they do "systemctl restart apache2" and it's jarring to have it
      A distributor who wants to (by default) delay kresd startup until it
      is accessed can ship the preset file included here, but leave the
      *.socket units enabled by default.
  9. 15 Aug, 2016 2 commits
  10. 28 Jul, 2016 2 commits