1. 12 Mar, 2019 1 commit
  2. 07 Feb, 2019 1 commit
  3. 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.
      42123aad
  4. 02 Jul, 2018 1 commit
  5. 16 Feb, 2018 3 commits
    • Tomas Krizek's avatar
      75387d4b
    • Daniel Kahn Gillmor's avatar
      systemd: drop ReusePort=true, no longer needed · cd23b590
      Daniel Kahn Gillmor authored
      ReusePort=true isn't needed because there is a single listening
      socket, which is shared across all instances.  Nothing needs to reuse
      the port.
      cd23b590
    • Daniel Kahn Gillmor's avatar
      More systemd service management cleanup · 0398a985
      Daniel Kahn Gillmor authored
      Please see discussion at:
      https://github.com/systemd/systemd/issues/8096
      
      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
      0398a985
  6. 01 Feb, 2018 1 commit
  7. 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
      kresd-control@1.socket).
      
      Users and packagers are also encouraged to use drop-in files for extra
      configuration or modifications to ensure compatibility with their
      distribution.
      4905226d
  8. 11 Jan, 2018 1 commit
    • 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.
      921feae2
  9. 20 Oct, 2017 1 commit
  10. 15 Aug, 2016 1 commit
  11. 28 Jul, 2016 1 commit